As easy to use as Trello for small teams, but scales up as you grow (although we probably cap out at 100-ish devs right now, not quite to Jira's level yet.)
(Full disclosure: CEO/Founder)
We deploy multiple times a day right now. Clubhouse is built with the option of a hosted version in mind, but we'd have to get to the point where we felt that things were stable and complete enough to say "ok, let's call this 1.0 and ship it."
I just requested a beta invite. Glad to see other businesses built on Clojure codebases!
https://github.com/lally/org-issue-sync
Open source, free to use.
However, FogBugz has its share of problems, and I'd gladly move to something else, if only there was something better. Must-haves that many companies miss are:
* flawless E-mail integration,
* task numbers,
* API that lets me attach code commit links (linking to GitHub) for reviews.
As to why not FogBugz — a number of reasons and annoyances. It's slow, expensive, too complex in many places, we've encountered a number of bugs over the years, and Fog Creek strongly resists changing FogBugz. Even relatively minor changes (we wanted FogBugz to detect cases based on "#1234" case numbers not a "Case #1234" string, because if you don't write in English, writing "case #1234" is unnatural) are refused.
It is a powerful extension that add project management features directly inside GitHub.
You would enjoy Task boards, Burndown charts and many other features without leaving GitHub's website.
(Full disclosure: I used to work for ZenHub)
It all depends on how you set it up, because it can be setup in myriad of ways. My first job the PM set up all sorts of convenience links to see different issues in different ways (sprint, status, owner, priority).
Now at my new job they just tell us over skype what query they typed in. Nothing wrong with that, but it's a lot more work than if it was setup differently.
Furthermore, the number of states a issue can be in can be different too. And it can be confounding to have too many states which mean nothing, or too few that don't mean enough.
It lacks strong organizational features, categorization, issue templates, search, and ability to save filters.
I've seen a lot of projects use it for pull requests and then disable the issue tracker, which is good and bad - you get a better tracker, you miss probably half of the bug reports.
GitHub issue tracking is not good enough to manage any kind of large project, JIRA is a bit of a beast.
I'd prefer having an integrated JIRA any day, though I do still strongly DISLIKE JIRA. There's still opportunity for something better IMHO.
(For very small teams, I find that's Trello, but Trello isn't really for large groups)