[mpdehaan2]

Despite having a gazillion issue trackers, something halfway between the two would be welcome.

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)

[kschrader]

We're working on something to split the middle at http://Clubhouse.io

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)

[annnnd]

Looks awesome - but please tell me you will have download-and-install option? Hosting solution is not acceptable to us and this could differentiate you from hundreds of others in this area.

[kschrader]

No download and install option... yet.

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."

[Ixiaus]

This is rad.

[uniclaude]

That sounds really interesting, we're still looking for the perfect fit in this area. Github issues are inconvenient for having a nice overview, Trello is good but not perfect for the multiple small projects of our company, and JIRA is definitely overkill.

I just requested a beta invite. Glad to see other businesses built on Clojure codebases!

[lallysingh]

I wrote something on top -- it imports github and google code issues and google tasks into emacs org-mode. Then I work on it from there. More than good enough for single users who've got to track a lot of crap.

https://github.com/lally/org-issue-sync

Open source, free to use.

[TeMPOraL]

As a die-hard Emacs/Org Mode user, thank you, thank you, thank you!

[jwr]

I can confirm there is an opening for something new. We use FogBugz (and pay quite a bit for the hosted version), because GitHub issues are too simplistic, and we hate JIRA.

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.

[seunosewa]

So basically, you want to (1) pay less for (2) a faster product that is (3) simpler and (4) less buggy, but also (5) implements most features that customers ask for.

[icehawk219]

I've been working on my own at https://getneutrino.com I built it for myself for the exact same reasons and then decided to open it up. It doesn't have e-mail integration or git/GitHub yet but both are being worked on and will probably be rolled out this weekend or next. I'll admit it's still a bit raw as it's still transitioning from "little project I built for myself" to a product.

[geoffreyy]

You could also use ZenHub [1].

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.

[1] http://www.zenhub.io

(Full disclosure: I used to work for ZenHub)

[girvo]

I really enjoy Breeze[0] at work. It's similar in concept to Trello, but aimed far more at project management and development. They just released a Gantt chart app that integrates with it, which is making some managers here really happy, heh.

[0] https://breeze.pm

[shocks]

SSL link doesn't work.

http://www.breeze.pm/

[girvo]

Oops! Thanks. I've also written a command-line interface for Breeze, which coupled with the BitBucket integration means I rarely even open the interface itself!

[nathanvanfleet]

I feel like everyone talking about JIRA aren't talking about the same thing. I stated strongly in a job interview that I currently used JIRA and knew it well. But was surprised that the new job didn't set theirs up in the same was as the job before.

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.

[wedesoft]

I am currently trying out Kanboard [1]. Not as slick as Trello but self-hosted and easy to install. Wonder whether anybody else has tried it and what they think about it.

[1] http://kanboard.net/

[michaelmior]

AFAIK, GitHub uses GitHub to build GitHub. I'd say GitHub is a large project.

[mpdehaan2]

I'm not positive they use it for issue tracking but they may. In my case, I was dealing with a single repo with 1000 or so contributors, and they were community people so it was very hard to get them to file quality structured bug reports, and the system didn't really allow for asking questions.

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.

[michaelmior]

I would agree with you on most points, but isn't categorization accomplished by tags?

[mpdehaan2]

They can be applied by the owner, but I guess I was thinking more of the ability to have a required 'component' field or a required field for the type of the ticket.