We've recently deployed Trac at our office. Part of that I would like to change the priority field for tickets as follows:
- priorities will be assigned a numerical value from 1 to 100 - 100 is the highet priority and 1 the lowest (or the other way around can work as well) - the top 50 (or trac.ini controlled value) prioritised tickets must have uniqe priorities (ie: if 100 is the highest priority, there can only be one ticket with a priority of 100, only one ticket with 90, etc, but multiple priority 50 or below tickets can exist). - default priority is 50 - the system must adjust ticket priorities in case of a conflict Any other pointers, warnings, concerns appreciated. My advice is to stick to some number of priorities for which you can articulate definitions, and just assign them. My project is using trivial/minor/major/critical/blocker working towards a demonstration and that's been good. If you really think you need an ordering like that, I suggest writing a plugin to give you an extra field in each ticket, which is basically sort order, and let that be separate, and thus allow manual sorting of tickets. This lets whoever wants to set the ordering set it, while not confusing it with an absolute priority.
pgpoIvrBaxjNI.pgp
Description: PGP signature
