#3490: "priority" management is riddled with bugs
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone:
Component: general | Version: 0.9.6
Severity: normal | Keywords:
-------------------------------+--------------------------------------------
I would like to use "priority" to organize priorities of individual
engineers. Unfortunately, it is frustratingly buggy. It appears not to
have been tested for values other than the canical (and for us not useful)
critical|major|minor|blocker.
My favorite example is below. Other examples include deleting a priority
name to which tickets were associated has the bad side affect of orphaning
those tickets. Even creating that name again does not un-orphan them.
Trac [/home2/mcprojects/webapps/trac]> priority add a8
Trac [/home2/mcprojects/webapps/trac]> priority add a9
Trac [/home2/mcprojects/webapps/trac]> priority add a10
Trac [/home2/mcprojects/webapps/trac]> priority list
Possible Values
---------------
a0
a10
a9
a1
a2
a3
a4
a5
a6
a7
a8
Trac [/home2/mcprojects/webapps/trac]> priority remove a10
Trac [/home2/mcprojects/webapps/trac]> priority remove a9
Command failed: priority a9 does not exist.
--
Ticket URL: <http://trac.edgewall.org/ticket/3490>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
