JIRA-Priorities: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
h1. JIRA priorities | h1. JIRA priorities | ||
Revision as of 16:06, 3 March 2015
| 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. |
h1. 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 | ||
| How many people using the feature are affected? Just a few (+1), some (0), quite many (–1) | ||
| Workaround | ||
| Is there an (easy) workaround? |
Other factors that might alter the priority: Compilation issues, legal issues, potential for data losses …