StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>We just went through the rather time consuming process of reviewing many (perhaps ten?) issue tracking systems to replace <a href="http://en.wikipedia.org/wiki/GForge" rel="nofollow noreferrer">GForge</a> which was getting in our way more than assisting. We considered free and commercial systems.</p> <p>To be frank, I was disappointed with <i>all</i> of the systems we reviewed. There's plenty of room for improvement in this domain.</p> <p>Many of them had poor interfaces (<a href="http://en.wikipedia.org/wiki/OnTime" rel="nofollow noreferrer">OnTime</a>, <a href="http://en.wikipedia.org/wiki/JIRA" rel="nofollow noreferrer">JIRA</a>, <a href="http://en.wikipedia.org/wiki/Bugzilla" rel="nofollow noreferrer">Bugzilla</a>). Generally, our engineers were OK with this, but it's important for our project managers, system integrators and <i>customers</i> to be presented with an interface that is clear and aesthetically pleasing.</p> <p>I was surprised to find that <i>very few</i> supported nested sub-issues. In the software world it is, of course, very common to break down a task (an issue or a new feature) into smaller components and assign them to different people. However, most systems couldn't do that - or couldn't do it well.</p> <p>Some systems were very powerful and configurable but practically <i>required</i> third-party extensions or plugins to make them useful. I really liked the flexibility of JIRA and <a href="http://en.wikipedia.org/wiki/Trac" rel="nofollow noreferrer">Trac</a> for example, but we would have had to invest considerable time to configure the systems to make them pretty or more functional.</p> <p>Naturally, they're not the only features we were concerned with, but this post is already getting too long!</p> <p>Of course, your requirements are going to be different to ours - I encourage you to figure out what you require and investigate thoroughly. </p> <p><a href="http://en.wikipedia.org/wiki/FogBugz" rel="nofollow noreferrer">FogBugz</a>, <a href="http://en.wikipedia.org/wiki/JIRA" rel="nofollow noreferrer">JIRA</a> and <a href="http://en.wikipedia.org/wiki/Trac" rel="nofollow noreferrer">Trac</a> were on our short list and they all had some great features. But in the end they were beaten by a product that - to me - was previously unknown: <a href="http://www.visionproject.se/" rel="nofollow noreferrer">VisionProject</a>.</p> <p>VisionProject is attractive and strikes a good balance between powerful and easy to use. The only downside we're seeing at the moment is that their new (since v4.0) Ajax-y interface has been a little buggy. However, we've had multiple bugfixes overnight and sometimes within a couple of hours - kudos to their über-responsive development team. </p> <p>We're still putting the system under trial and, although not perfect, it's comparing extremely favourably against all the other contenders.</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