Isn&#x27;t that the problem, though? GitHub has one Issue tracker that is &quot;good enough&quot; for most projects I&#x27;ve worked on, and gets better over time because GitHub dog foods it (even if they don&#x27;t always see some of the large open projects issues with it). Bitbucket has two Issue trackers, a &quot;sort of useful&quot; minimalist one that is worse than GitHub&#x27;s and an upsell to Jira which is maximalist overkill for any project I&#x27;ve worked on. Atlassian doesn&#x27;t have much incentive to make Bitbucket&#x27;s issue tracker any better than it&#x27;s current &quot;almost decent&quot; because it wants to upsell Jira. You can pretty much assume that Atlassian only works in Jira themselves.<p>(Similarly, VS Team Services has only one issue tracker and I&#x27;d rather use that than both of Atlassian&#x27;s offerings, even though it&#x27;s almost equally maximalist with Jira, mostly because they clearly dog food it <i>and</i> don&#x27;t try to upsell into it from a worse system that nobody wants to use.)