Ticket #4338 (closed defect: duplicate)
Opened 5 years ago
Last modified 5 years ago
Allow more possibilities for status
| Reported by: | bram@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.2 |
| Severity: | normal | Keywords: | status |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
For a production quality triage bug tracking system, trac is lacking an extra state for bugs. For our purposes this is "resolved" (e.g. tester files bug (new)=> bug goes to developer (assigned) => developer fixes bug (resolved) => tester verifies and closes bug (closed).
Many other development cycles use something simpler, or more complex as well. Trac should either be providing at least a 4-state resolution process, or allow you to define your own states.
Attachments
Change History
comment:1 Changed 5 years ago by sid
- Milestone 0.10.3 deleted
- Resolution set to duplicate
- Status changed from new to closed
comment:2 Changed 5 years ago by cboos
See WorkFlow actually, as NewWorkflow is ... the older proposal ;)



Defining a custom ticket workflow is already proposed in #869. See also NewWorkflow for an overview of the proposed system. This is intended for milestone:0.11.