This reminds me a bit of Bee[1] which puts a native Mac interface on top of existing issue trackers (GitHub, JIRA, FogBugz). On the one hand, Bee's approach seems like a win in the short term because people don't have to switch where there data lives or buy in to an off-premise service if that's not what they want. Longer-term, though, the data model of the existing systems could prove to be limiting if you've got good ideas for how to change the approach here.
Issue tracking "at scale" is hard for the same reason that a lot of software becomes complicated: when applied to the real world, new workflow needs and such pop up frequently. As an example: security issues that may need to have a restricted audience for a time. The release model for web-based software is different from that of desktop or mobile software.
There's plenty of room to make this better! Good luck in finding a winning path forward!
Issue tracking "at scale" is hard for the same reason that a lot of software becomes complicated: when applied to the real world, new workflow needs and such pop up frequently. As an example: security issues that may need to have a restricted audience for a time. The release model for web-based software is different from that of desktop or mobile software.
There's plenty of room to make this better! Good luck in finding a winning path forward!
[1]: http://www.neat.io/bee/