- Status New
- Percent Complete
- Task Type TODO
- Category Translations
- Assigned To No-one
- Operating System All
- Severity Medium
- Priority High
- Reported Version 1.0 devel (github master)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Flyspray - The bug killer!
Opened by peterdd - 07.04.2016
Last edited by peterdd - 16.03.2018
Opened by peterdd - 07.04.2016
Last edited by peterdd - 16.03.2018
FS#2114 - Standardize the priority meaning across flyspray translations
Standardize the priority meaning across flyspray translations.
Idea:
0 - priority unset (database field default value)
1 - defer (or very low priority, often results the task is defered, see “Eisenhower principle”)
2 - low
3 - normal
4 - high
5 - very high
6 - flash (house burns, catastrophic event, website down, “boss” decision)
Some other software (other task planers/ email programs) use a 1-5 step priority. So an export feature to other software may merge priority 6 to priority 5 for such software.
In 2012 meaning was changed only in english translation.
Before normal was priority 2 in a 1-6 range, after it is priority 4 in a 1-6 range.
It should be IMHO 3 in that 1-6 range.
Here a little comparison of current priorityx translations across language files
in current flyspray master:
As you can see, many languages still have the pre 2012 meaning and some have the priority meaning of the 'en' change in 2012 now applied to their translation. (en,fi,fr,no,ro)
I still suggest a meaning like it is in the de.php , as this is probably a good compromise between pre 2012 and 2012 english priority version.
Also better for migration between other types of bug/task trackers.
As said on GitHub I'm not that fond on having "defer" as a priority... that could be a "very low" associated with a change in the due version, also you have a similar thing between closing reasons.
I'm ok with having 3 = normal, then low/very low, then high/very high/urgent