[Trac-tickets] Re: [The Trac Project] #2220: priority/severity misunderstanding.

[The Trac Project]

#2220: priority/severity misunderstanding.
---------------------------+------------------------------------------------
 Reporter:  dju`           |        Owner:  jonas
     Type:  defect         |       Status:  new  
 Priority:  normal         |    Milestone:       
Component:  ticket system  |      Version:  0.9b2
 Severity:  normal         |   Resolution:       
 Keywords:                 |  
---------------------------+------------------------------------------------
Comment (by cmlenz):

 cboos proposed and implemented the extension of the Trac ticket model by a
 ”ticket type“ field. And after much debate and tweaking, the proposal
 was merged.

 Now that enhancement requests were no longer second clas citizens in Tracs
 ticket system, the severity field seemed out of place. “Severity“,
 defined as relating to “something bad or undesirable“ by the Oxford
 American Dictionary, does not make much sense for enhancement requests or
 tasks.

 However, the severity ''values'' such as “blocker" or “trivial” do
 make sense for enhancements: you can have an enhancement ticket that
 blocks a release, i.e. it must be implemented. You can have “trivial”
 enhancements or “critical” enhancements. I think these values are
 quite a bit more intuitive than the generic “highest”, “higher”,
 etc values, which only make sense when you look at them relative to other
 tickets (i.e. you could just as well use some yucky star graphics ;-) )

 So, following the lead of [http://www.atlassian.com/software/jira/ JIRA],
 we moved the severity values over into the priority field for new Trac
 environments, and disabled the severity field by default. (Note that this
 is not true for upgraded environments, which is another story altogether).
 As cboos states, another reason was to keep the number of default ticket
 fields down to something managable.

 Looking at other issue trackers, I wasn't able to find any mainstream
 systems that by default provide two fields to convey the importance of a
 ticket, and also provide a field to differentiate between types of
 tickets. And I think that's not a coincidence.

 Also, I'm pretty sure this is a dupe, but I have to yet find the original
 ticket...

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/2220>
The Trac Project <http://trac.edgewall.com/>