Menu
▾
▴
#380 Priority: use High/Low/etc value instead of numerical values
I cannot believe that there are still bugtrackers around using numerical priority values such as 1 to 5, where you never know whether priority 1 is the highest or the lowest priority.
This is an issue that has been known for years, and all decent bugtrackers have switched to a non ambiguous system where labels such as "highest, high, low", etc are used instead.
I seem to remember the very software SF is using has this already fixed in its latest version. For god's sake when are you going to upgrade??
Greetings, every field is fully customizable, so if you don't like it ask to phpMyAdmin administrators to change it.
Oh, now I see why I felt like i had gone back to the past.
Thanks and sorry for the confusion
You are welcome!
Can you explain the procedure to customize labels for bug priority?
I remember the pre-Allura time when bug priority was associated with a color on the summary page: severe bug needing urgent repair painted red, low priority blue and in-between with gradient colors.
It was visually easy to focus on the important issues. Is it possible to reimplement this feature?
Greetings, of course I can.
Click here, click on New Field, label it as Priority, in Type choose Select and in Options type:
The * means "default".
I use another method for my project, I edited searches, click here to do so.
Field management: Admin - Tools - Bugs - Field Management.
Search management: Admin - Tools - Bugs - Edit Searches.
Fields and searches should be a replacement for this, but if you like to ask for this feature you can vote this ticket, it should be the same.
Last edit: Zangune 2015-02-23
Thanks a lot.
The trick was to go Admin->Tools->xxx->yyy Management. I think I'll pay more attention to this page.
You are welcome!
This is closed/invalid, right?
Invalid, right.
But kept open for visibility?