JIRA-Priorities: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Make a more readable link to the authoritative source.) |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
= | = JIRA priorities = | ||
This is an attempt to make the selection of the 'right' priority of a JIRA issue more transparent. | |||
This is an attempt to make the selection of the | |||
''This is work in progress'' | ''This is work in progress'' | ||
The authoritative resource is https://bugreports.qt.io/secure/ShowConstantsHelp.jspa?#PriorityLevels | The authoritative resource is [https://bugreports.qt.io/secure/ShowConstantsHelp.jspa?#PriorityLevels on Jira] - this page should be understood only as a tool. | ||
==Bugs== | == Bugs == | ||
Start with priority 3. Then raise, or lower the priority based on the | Start with priority 3. Then raise, or lower the priority based on the bug's severity, visibility, whether it's a regression, or whether there's a workaround. | ||
{| | |||
|- | |||
| Default Priority | | Default Priority || 3 || | ||
| 3 | |||
| | |||
|- | |- | ||
| Severity | | Severity || -1 || Does the bug make the application unusable (crashes/hangups …)? | ||
| -1 | |||
| Does the bug make the application unusable (crashes/hangups …)? | |||
|- | |- | ||
| Regressions | | Regressions || -1 || Does the bug break code that worked in (recent) previous versions? | ||
| -1 | |||
| Does the bug break code that worked in (recent) previous versions? | |||
|- | |- | ||
| Visibility | | Visibility || +1/0/-1 || How many people using the feature are affected? Just a few (+1), some (0), quite many (–1) | ||
| +1/0/-1 | |||
| How many people using the feature are affected? Just a few (+1), some (0), quite many ( | |||
|- | |- | ||
| Workaround | | Workaround || +1 || Is there an (easy) workaround? | ||
| +1 | |||
| Is there an (easy) workaround? | |||
|} | |} | ||
Other factors that might alter the priority: Compilation issues, legal issues, potential for data | Other factors that might alter the priority: Compilation issues, legal issues, potential for data loss, etc. | ||
== Tasks/Suggestions == | |||
Latest revision as of 14:20, 29 February 2016
JIRA priorities
This is an attempt to make the selection of the 'right' priority of a JIRA issue more transparent.
This is work in progress
The authoritative resource is on Jira - this page should be understood only as a tool.
Bugs
Start with priority 3. Then raise, or lower the priority based on the bug's severity, visibility, whether it's a regression, or whether there's a workaround.
| Default Priority | 3 | |
| Severity | -1 | Does the bug make the application unusable (crashes/hangups …)? |
| Regressions | -1 | Does the bug break code that worked in (recent) previous versions? |
| Visibility | +1/0/-1 | How many people using the feature are affected? Just a few (+1), some (0), quite many (–1) |
| Workaround | +1 | Is there an (easy) workaround? |
Other factors that might alter the priority: Compilation issues, legal issues, potential for data loss, etc.