Loading Profile...
Add the ability to put bugs and chores into Delivered and Accepted/Rejected states
It would be nice to be able to mark a bug or chore as "Delivered" and "Accepted", like how Features work.
So then, the developer who fixes the bug can mark it as finished, when it's put on the test or live site, can mark it as Delivered, and the story requester can mark it as Accepted.
So then, the developer who fixes the bug can mark it as finished, when it's put on the test or live site, can mark it as Delivered, and the story requester can mark it as Accepted.
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Bugs need to be delivered and accepted. Chores do not. -
Inappropriate?Joe, right now Tracker has a rigid workflow cycle for Features, Bugs, and Chores. The workflow tracks very well with the needs Pivotal has in developing mostly greenfield websites in small teams. We understand that for larger projects with distinct QA and deployment teams, multiple iterations of Deliver and Accept might be needed. We're still investigating how best to implement configurable workflows.
For your use case, would the ability to add an arbitrary number of Deliver --> Accept repeats be sufficient? Story flow would then be something like Start --> Finish --> Deliver --> Accept [--> Deliver --> Accept]*
EMPLOYEE
