On 28 Jun., 08:16, Risto Kankkunen <[EMAIL PROTECTED]> wrote: > But a mere "task" probably doesn't need to go through Q&A, for example.
In begining of project most development consists of tasks (make design, write manual, ...) and of course needs QA, maybe not testing but reviewing. > > I wonder how common or useful it is to change a ticket type after it > has already gone through some state transitions? I think the type of > the ticket (enhancement, defect, task) should be pretty obvious after > some person from the project has looked into it. One might even argue > that the type should only be set by a project member, not by the > submitter. Examples: Customer complains "This is a bug". Developer gets to analyse it and agrees. Project manager gets it and says: "Oh no, that was not part of contract, it's an addon we can get money for it.". >From QA point of view: It matters if you have 10 new bugs per week or 5 new bugs and 5 feature requests, whilst developers solve only 7. The predicted delivery date (and the blame for the delay) strongly depend on that. > > So there could be a couple of general states (submitted, ...) and then > type-specific states after the type has been decided. > > Also, rather than to morph or copy tickets, it can be useful to add > subtickets with suitable types (assign several tasks as subtickets to > an enhancement etc.) That is similar to an advanced feature I know from MKS. They split the change request and subsequent issues (for multiple version or module owners). We considered it to be a nice idea, but had trouble to use it properly. Got a hard to track what belonged together. A single quick overview was not possible anymore. Properly done your idea for sure would be helpful for bigger projects. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
