Disagree. Maybe for small projects with small teams and simpler workflows but I've found the exact opposite. I love GitHub, and it's issues system is great for

Disagree. Maybe for small projects with small teams and simpler workflows but I've found the exact opposite. I love GitHub, and it's issues system is great for specific issue management for specific projects/modules. It could be better, but it's pretty solid. However - once you get into wider project management which has multiple modules/repos under it then it's functionally useless for managing issues. No visibility across repos. Nor should there be - it's not what it's trying to solve. Take my companies case: we use GitHub a lot but we also use Jira, and they work really well together. We use a (forked) version of GitFlow to create branches and link them to the JIRA task and when we create a PR (to be reviewed via Github) it notes what issue it's related to. Github's diffing, commenting, and so on, still used as normal. It's great. For for bug tracking, story breakdowns, burn down, spring planning, etc etc - this is Jira's bread and butter (after you configure it at least). And these are not things GitHub is going to be good at - and it shouldn't try! Different use cases. Using one to do what the other does would be horrible. Compare with some OSS projects I run that don't need all I mentioned above and yes, obviously, I use GitHub exclusively... because it's the best tool for the job.