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&#x27;s approach seems like a win in the short term because people don&#x27;t have to switch where there data lives or buy in to an off-premise service if that&#x27;s not what they want. Longer-term, though, the data model of the existing systems could prove to be limiting if you&#x27;ve got good ideas for how to change the approach here.<p>Issue tracking &quot;at scale&quot; 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.<p>There&#x27;s plenty of room to make this better! Good luck in finding a winning path forward!<p>[1]: <a href="http:&#x2F;&#x2F;www.neat.io&#x2F;bee&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.neat.io&#x2F;bee&#x2F;</a>