Modify ↓
#4338 closed defect (duplicate)
Allow more possibilities for status
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.2 |
| Severity: | normal | Keywords: | status |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal 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 (0)
Change History (2)
comment:1 by , 17 years ago
| Milestone: | 0.10.3 |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.