> I guess if GH had its own version that would be slightly easier.
GitHub does have its own version. You can organize GitHub Issues into GitHub Projects. GitHub Projects have all sorts of iteration planning tools and team management tools and metrics reports that light up as you configure it. I've heard and seen screenshots that even more light up if you have an Enterprise Cloud account and/or pay a GitHub Consultant (they way some companies love their overpaid Jira Consultants).
I've tried to make the case for GH Projects to employers before. Supporting only one tool is very nice from a developer experience viewpoint. Of course, that's not something management often cares about, and Jira isn't always just software development, but also sometimes incident tracking and support desk and everything else and having more "synergy" there appeals more to some sorts of managers.
GitHub does have its own version. You can organize GitHub Issues into GitHub Projects. GitHub Projects have all sorts of iteration planning tools and team management tools and metrics reports that light up as you configure it. I've heard and seen screenshots that even more light up if you have an Enterprise Cloud account and/or pay a GitHub Consultant (they way some companies love their overpaid Jira Consultants).
I've tried to make the case for GH Projects to employers before. Supporting only one tool is very nice from a developer experience viewpoint. Of course, that's not something management often cares about, and Jira isn't always just software development, but also sometimes incident tracking and support desk and everything else and having more "synergy" there appeals more to some sorts of managers.