Hi, > http://trac-hacks.org/wiki/AgileTracPlugin seems to be an interesting > approach to tackle agility, see also http://www.agile-trac.org/roadmap. > from a complete user perspective I see some overlap with another agile modification (see www.agile42.com). While choice is good, I think a lot of projects replicate similar work that belongs to the trac core in my opinion.
* Ticket types vs. ticket domains vs. ticket views agile-trac replicated the ticket system in the first iteration in order to create a new ticket domain. Now they are looking into ticket views. As an end user I'm looking for requirement management, test case management, ticket system, and other domains, completely unrelated to each other. The current ticket type implementation is to simple to suport my needs here and also the needs of some plugin developers (showing and hiding fields based on the ticket type). Trac-core should export its ticket system as a basic ticket core. So that everybody could create ticket domains with configuration on top of it, e.g. one domain for requirements, one for user stories and one for bugs. Ticket types itself are still a good feautre within each ticket domain. * Ticket linking The most important plugin in this area is the master ticket plugin that defines a parent child relationship between tickets. But what about duplicates? Other types of realtionsships like Requirement -> User Story -> Task? How to easily create a new Task from a User stroy. agile42 has a good (end user friendly) implementation for this. support for interlinking belongs to the core. Definition of what a link does and how it helps to create a workflow belongs into a plugin and the configuration. * Ticket display All agile plugins have the problem that they flood the ticket timeline with "status changed" information. This should be filtered in the timeline. Again agile42 has one idea for this to support a tabbed interface for "ticket discussions" and "ticket status changes" and also another one for ticket modifications. This tabbed interface belongs into the core. I could think of plugin that shows another tab with related checkins for a ticket, or other "linked" information. * Duplicate handling This does not really fit into the above summary, but it is a week point in trac. Is the other duplicate ticket closed or is it still active? How do you now, without looking into the master ticket of the duplicate. How do you now the master ticket? You have to tell it in the comment that you marked another ticket as a duplicate and the status of the ticket is closed. I was fooled by the fact multiple times, since a ticket was closed but was not resolved. * Support for versions I know a few people having problems with the milestones and software versions. In which version is a bug fixed? And in which version is it still open? Milestones are milestones not versions. A milestone is not generally a release of a software. It can be any intermediate step that will help people to enforce some progress at some time. versions are versions and as long as a bug is not fixed (or verified in a specific version) it is open for all dependant versions. If a bug is closed in the trunk it is closed in the trunk, but not in any previous release. Generally you can pinpoint a bug to specific version and if you are lucky to a specific checkin. It would be wonderful if trac would understand the concept of versions. This is only input from an end user perspective. Best regards Dirk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
