Ticket #1870 (closed enhancement: wontfix)
Opened 7 years ago
Last modified 7 years ago
Add "Caused by" option to bug resolution
| Reported by: | ben@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.8.4 |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
I think it would be great to have some way of tracking the cause of bugs in loose categories, i.e.
"Fixed: #1873. Bug caused by planning errors in the database structure."
Which would resolve the bug and set the "Caused by:" property to "Planning Errors". The types of errors could be configurable via trac-admin, and you could make some great inferences by visualizing the data over time.
You could even pull keywords from the rest of the log, i.e.:
"Closes #1187. Bug caused by planning errors in the database format."
"Fixes #1873. Bug caused by unjustified assumptions about the database foreign key structure."
"Fixes #2853. Bug caused by lack of automation in the database setup."
You've clearly got database problems.
- Ben
Attachments
Change History
comment:1 Changed 7 years ago by eblot
comment:2 Changed 7 years ago by mgood
- Resolution set to wontfix
- Status changed from new to closed
Generally the solution would be listed in the comments when closing the ticket. If you have some defined categories you can use the TracTicketsCustomFields to add a dropdown field for these. The keywords field is also a place some of this type of information can be put.



This seems a non-general case, and I would recommend to use the 'custom field' feature to implement such a feature.
I don't think this requirement is generic enough to be added to the main trunk.