Edgewall Software

Opened 19 years ago

Last modified 15 years ago

#2220 closed defect

priority/severity misunderstanding. — at Initial Version

Reported by: dju` Owned by: Jonas Borgström
Priority: normal Milestone:
Component: ticket system Version: 0.9b2
Severity: normal Keywords:
Cc: dju@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

This covers several questions:

  1. Why are default priority values going from "trivial" to "blocker", and default severity list is empty? IMO, "trivial" to "blocker" values express the idea of severity (importance of the defect/enhancement/task), and default priority would better go from "lowest" to "highest", just as in the 0.8 series. What are the reasons of this switch?
  1. Why has the "normal" "priority" (ex severity) doesn't exist by default?
  1. Why is the severity (ex priority) list empty by default?
  1. As "priorities" (ex severities) apply to any type of ticket (defect/enhancement/task), I'd like to see "blocker" not appear by default, as it has, I think, no meaning for enhancements and tasks, and as "critical" and "blocker" look very similar for bugs and could be merged.

Change History (0)

Note: See TracTickets for help on using tickets.