Opened 9 years ago
Closed 8 years ago
#575 closed enhancement (worksforme)
Get your priorities fixed
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | BA trunk | Version: | |
| Keywords: | Cc: |
Description
This Trac installation should get some improvements:
- Delete current priorities, enable the serverity field, use the current priorities as serverity, use priority with values from high to low.
See http://trac.edgewall.org/ticket/1861 and http://trac.edgewall.org/ticket/2220 as well as ITIL like here for example: http://itservicemngmt.blogspot.de/2007/06/incident-priority-what-everyone-should.html where
- Urgency (ITIL)
- Priority (Trac)
- Impact (ITIL)
- Severity (Trac)
- Also at least one additional component "none" would be great for tickets like this one.
- Also the versions would be nice. With a subversion trigger on commits you can filter the tags and automatically fill the Trac versions. I can help with that if you want.
In fact I can help with all of this. If you want a shell script to do above changes I would be glad to provide it.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 8 years ago
I am happy with our trac. I agree that a 'general' priority field would be a good catch-all.
comment:3 by , 8 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Severity is enabled, it is displayed as the color of the ticket. Its ok, there arent that many tickets or developers that this would become unmanageable. I know I should have upgraded trac ages ago, but I have learned the linux 'If it aint broke dont fix it' mantra the hard way.