StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhere can I find a comparison of Distributed (and Offline?) Issue Trackers?
text
Body
copied!<p>I'm looking for a fairly recent in depth comparison of currently available Distributed and hopefully Offline Issue Trackers.</p> <p>I've found this <a href="http://heapkeeper-heap.github.com/hh/thread_298.html#post-summary-hh-1076" rel="nofollow noreferrer">http://heapkeeper-heap.github.com/hh/thread_298.html#post-summary-hh-1076</a> which is decently recent and covers a number of solutions, but isn't up to date and IMO wasn't as researched as it could have been, so I'm looking for similar comparisons.</p> <p>Full disclosure, I've become the primary maintainer of the TicGit distributed issue tracking system <a href="http://github.com/jeffWelling/ticgit" rel="nofollow noreferrer">http://github.com/jeffWelling/ticgit</a> . I'm looking for a comparison to see if I'm reinventing the wheel with my development with TicGit. I want a distributed offline issue tracking system, which in a perfect world would be written in Ruby, and which supports a web interface. The web interface could be a daemon or it could just be HTML files I publish somewhere. Ticgit already does these things, but if someone else out there does them better or has the same feature list with a larger community..</p> <p>I found this comment <a href="http://github.com/blog/411-github-issue-tracker#comment-1722" rel="nofollow noreferrer">http://github.com/blog/411-github-issue-tracker#comment-1722</a> which comes from someone knowledgeable on the subject, which says storing tickets in git causes you to lose a lot of functionality, but doesn't elaborate. I don't understand why that would cause a loss of functionality.</p> <p>If you can't suggest a comparison, whats your favorite Distributed Issue Tracker and why? :)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload