They also support Mercurial, which I personally find to be a way better scm tool than git.

Not trying to start the classic hg vs git debate, just saying that it's great to have the option.

Bitbucket server is written in Java while Bitbucket.com in Python. Those are two different products. That's why the Enterprise version supports only GIT.

Check our RhodeCode for Enterprise SCM tool that supports Mercurial too.

And I hope GitHub stays incomplete! I don't need hierarchical access control to decide who can add, remove, and list issue labels, or whatever, just because some pointy-haired enterprise boss came up with that idea five minutes ago.

We are using https://www.zenhub.com/

Personally (and I'm not sure if JIRA fixes this, but Trello gets around it), the biggest issue I have is that Github treats repositories as the only possible context. Say a bug comes in that covers multiple repositories (e.g.: requires a mobile app fix and a backend fix), then you need to create two completely seperate issues and remember to link them manually. This breaks down very quickly. I would much rather issues to optionally exist at an organisation level, with per-repository sub issues stemming from that organisation-level issue.

It also means that someone submitting bugs, say from customer support, must try and figure out where the issue is in order to log it. It's a huge hassle and most just give up and ping an engineer on Slack which is incredibly inefficient.

Trello gets around this by letting you create a "master" issue and link to the individual repository issues. It means engineering can have a bug inbox and triage from there. Still a huge pain and not ideal.

Github also has the "Projects" feature, but it is useless IMO due to the above issue - I wish projects would work at an organisation level.