In a lot of ways, GitHub Issues is to Issue Trackers what Google Reader was to RSS Readers.
It's good enough and "cheap/free/low-friction" enough to use once you are using GitHub, that for a smaller organization, it's a total no-brainer.
But as your team grows, as your org grows, you really start to hit the weak points very quickly.
The benign neglect that GitHub shows Issues is, as a paying customer, incredibly frustrating. It's also a real head scratcher, considering how much they are leaving on the table in terms of opportunities to create additional revenue.
Personally, I'd love to see GitHub add a KV-store type feature to Issues (so you can associate arbitrary meta-data with issues) and then an "app store" for "plugins" or "extensions" that different companies can provide and customers can pay for as part of their GH subscription (a la ZenHub).
It's good enough and "cheap/free/low-friction" enough to use once you are using GitHub, that for a smaller organization, it's a total no-brainer.
But as your team grows, as your org grows, you really start to hit the weak points very quickly.
The benign neglect that GitHub shows Issues is, as a paying customer, incredibly frustrating. It's also a real head scratcher, considering how much they are leaving on the table in terms of opportunities to create additional revenue.
Personally, I'd love to see GitHub add a KV-store type feature to Issues (so you can associate arbitrary meta-data with issues) and then an "app store" for "plugins" or "extensions" that different companies can provide and customers can pay for as part of their GH subscription (a la ZenHub).