JIRA-Priorities: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 24: | Line 24: | ||
|} | |} | ||
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 == | == Tasks/Suggestions == | ||
Revision as of 09:57, 25 February 2016
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
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 https://bugreports.qt.io/secure/ShowConstantsHelp.jspa?#PriorityLevels - 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.