The new Projects is like Jira without the top-down “Jira Align”-style features. So you can have issues from multiple projects show up in a board, that board can

The new Projects is like Jira without the top-down “Jira Align”-style features. So you can have issues from multiple projects show up in a board, that board can look like Trello… but if you want to duplicate the card’s custom fields to a different board, it gets trickier. The card and its data lives in the board it’s created in. You end up having to do lots and lots of hacky things with GitHub Actions and the Projects GraphQL API to make it work the way you want it to. And granted, it’s cool you can do that. Having CI events fire for every issue created is awesome. But sometimes you fight their defaults soooo much, that just customizing Jira seems easier at times. Don’t get me wrong, if you’re all in on GitHub, you’ll do okay with it. Especially if you write Actions to feed data in or out of it using the GitHub CLI and/or API or GitHub-script CI actions. But you’ll also probably miss Jira if you’ve used it as a power-user. Especially if you want to do advanced things with boards and cards and issues that it might not offer by default out of the box. And GitHub’s GraphQL API is powerful but also weirdly and frustratingly restrictive at times, particularly with usage and query limits. An easy SQL query for GitHub to run internally is opaque and confusing for a third-party to develop - GitHub knows what things are easy to hard to query by design but outside of GitHub you just make the API calls and hope it scales well to larger projects, or find out the hard way when it fails.