Using Severity for Trac Tickets

Question

I regularly use Trac as a team at work, as well as in my own university project. In both cases, I never felt the need to use a property severityfor a ticket. I feel that with the help of properties typeit prioritygives all the information I need, and I cannot think of anything in common with a property severitythat would not be redundant. Does anyone have a good opportunity for severity-property?

Answer 1

You can consider priority and severity as orthogonal values.

The severity may indicate how expensive the error is: a low degree of severity may be “the color of this icon is incorrect”, and a high degree of severity may be “computer hunting down and killing a user”.

The priority is how to urgently solve the problem. An icon that uses the corporate color of a corporate competitor may have high priority, while a fatal error that may occur once every million years may be low priority.

You can then work on things based on the severity priority; what is medium severity and medium priority may be more important than what is low severity and high priority.

OR

, - . , , . , , , . ( , , , . , .)

, , // . .

_{Discloser: Trac}

Answer 2

, , , , , .

: Trac () . , , " ", " ", " " . , , , , .

, , . "no_problem" "needs_concerted_effort" "panic_attack". ( , .) , - , ; , - , .

: , , , , . "", "", "", "" "".