Opened 19 years ago
Closed 19 years ago
#1870 closed enhancement (wontfix)
Add "Caused by" option to bug resolution
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.8.4 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal 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 (0)
Change History (2)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Resolution: | → wontfix |
---|---|
Status: | new → 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.