If I were starting with a clean slate, I would probably choose Trac for
an open source issue tracker. Pivotal requires licenses and hosting,
plus if we started using it (or Trac) now we'd have to migrate all the
current Jira stories/tasks/subtasks across to it.
For now I would prefer to continue with Jira on the basis that it's
"good enough", and that the kind folks at Codehaus are hosting it for us.
Cheers,
Dan
Mauro Talevi wrote:
Shane Duan wrote:
To do what JIRA dose right now, if we add all the stories to JIRA
(which is cumbersome)
For example, the list the Liz sent could have been there and it would
be easier to see the work being done.
Of course, and it can be done in Jira. Not that I have anything
against other tools, but Jira is setup and has equivalent
functionality to other tools. Don't really see the benefit in moving
to another tool.
For the stories Liz listed, IMO the best approach is an single issue
with sub-tasks (which are issues themselves). Cf
http://jira.codehaus.org/browse/JBEHAVE-15.
Or perhaps I'm missing something - what the problem you see in using
Jira?
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
