[TIP] Looking for a decent issue tracking system

Kumar McMillan kumar.mcmillan at gmail.com
Mon Jun 22 11:30:08 PDT 2009

On Thu, Jun 18, 2009 at 9:46 AM, Yannick Gingras<ygingras at ygingras.net> wrote:
> Greeting Python Testers,
>  the scope of my inquiry is a bit broader than just testing but since
> testing is a major entry point for new issues, I assume that some of
> you can help me find the tools that we are looking for.
> We are looking for an issue tracker that deals well with iterative
> development.  The ideal tool will automatically compute our velocity
> and will automatically plan the next iteration given only priorities
> for open issues.  One alternative is for the tool to let the project
> manager plan the iteration by hand but to warn him if he puts in more
> stuff that can fit in the iteration given the current team velocity.
> We are also looking for a way to have sub-projects and sub-tickets
> that can be looked at independently but that will be summed up together
> when looking at the higher level road-map.

I really like doing scrum-style, iterative development using Pivotal
Tracker http://www.pivotaltracker.com/  It does a lot of what you are
asking, like precompute velocity.  It even goes so far as to restrict
what you put in a sprint until your velocity is ready to handle more
stories :)  You pretty much have to succumb to these kind of decisions
though, it is not as customizable as something like Trac or Jira.  I
highly recommend it though.

> Trac offers some of these features with add-on modules but the
> sub-project support is not very good.  Redmine has sub-project but the
> way it is implemented makes it almost unusable for planing purpose
> since versions can't be share between sub-projects.  Let me give you
> an example.  If you implement the Frobnoz application than has both a
> Data-Import and Billing sub system, the Redmine tickets for version
> 25.0.1 of the billing sub system won't show up in the Frobnoz road-map
> since Redmine treats billing-25.0.1 and frobnoz-25.0.1 and two
> completely unrelated software versions.
> On the other hand, both Trac and Redmine are very good if you only use
> them as bugtracker.  I'm sure that there is a tool out there that is
> booth good at a bugtracker and as a feature planner.  Do you guys have
> any recommendations?  Any of you using different tools for bugtracking
> and for project planning?  Are there any combinations that plays well
> together?
> --
> Yannick Gingras
> http://ygingras.net/
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python

More information about the testing-in-python mailing list