Ticket Workflow
As well as some TracConventions and CommitConventions to help developers work together, we also have a non-standard Trac ticketing workflow to aid the collection, checking and progress on tickets. The workflow is as follows:
Step | Description | Next Steps
|
---|
New | Ticket has been submitted, but not reviewed by anyone | new_needinfo or confirmed
|
Confirmed | Ticket has been reviewed by one of the developers and confirmed, or accepted as a sensible enhancement | needinfo, accepted or resolved
|
New_NeedInfo | The ticket has not been confirmed, and further information is required before we can confirm it. | new_needinfo, confirmed or resolved
|
NeedInfo | The ticket has been confirmed, but more information is required from the reportee or other users to complete development work | confirmed, accepted or resolved
|
Accepted | A developer has accepted the ticket (bug, task or feature request) and has claimed it to work on it | resolved
|
Resolved | The ticket has been resolved, either because it can't be recreated, because it isn't valid, because it is a duplicate, or is already fixed, or (hopefully) because a fix has been created |
|