Github issues isn't really a team management tool IMO. It's more of a support desk for users of that specific repo. You can try to bend it into a team managemen

Github issues isn't really a team management tool IMO. It's more of a support desk for users of that specific repo. You can try to bend it into a team management tool, but it is limited and probably won't work well unless the team is tiny. I've seen Github issues work well in a few cases: - Open source project needs a public facing place to collect tickets specific to that repo - works great! - Internal tools team needs an easy way to collect bugs and issues from other teams in the company using the repo. - You are a two-person start-up with exactly one repo and just don't need anything more complicated yet. But beyond that, you will pretty quickly hit the limits of GitHub issues. Assuming all your code isn't just in one repo, it will become impractical to manage tasks across projects. Jira is a pain to learn and configure, but it works pretty well after you get it set up and it scales well as the company scales. There are probably 20 other task tracking tools that work well enough for a small team. But Github issues is probably too limited except for a tiny team IMO.