Ticket #2511 (closed enhancement: duplicate)
Opened 6 years ago
Last modified 4 years ago
Adding support for a testing ticket status
| Reported by: | wichert@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.9.2 |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
For a lot of projects I need the ability to set the status for an issue for testing. This is a seperate step between active and resolved where an issue should be resolved, but has not been certified to be resolved by full testing, which is (should) be done by other people.
To support this I created a patch which added a new ticket status called 'testing', modified the milestone and roadmap to show that tickets in a testing status seperately and updated the unittests to reflect the new possible actions.
In order to make this easier to use I also modified the trac-post-commit subversion hook: I added a --testing parameter which tells the hook to mark an issue as testing instead of fixed. The default is set to fixed in order to preserve backwards compability, and since I suspect that most trac installs are for small projects which do not have a need for a seperate testing status.
Attachments
Change History
Changed 6 years ago by wichert@…
- Attachment trac.testing.diff added
comment:1 Changed 6 years ago by mgood
- Resolution set to duplicate
- Status changed from new to closed
#869 will address the need for customization of the workflow.
comment:2 Changed 4 years ago by anonymous
NO project is too small for a testing status!!
testing status support