-
Support Request
-
Resolution: Duplicate
-
Medium (View bug fix roadmap)
-
None
-
3.0.3
-
None
-
Standalone
Will the severity field be intergrate into the next release of JIRA? Both severity and Priority are very important for tracking the bugs.
- duplicates
-
JRASERVER-886 A Jira 'Priority' is really 'Severity' - could we specify a Severity and a Priority instead?
- Closed
- relates to
-
JRASERVER-21293 Rename any system field via the admin section
- Not Being Considered
[JRASERVER-5500] Severity field is not a default field
Workflow | Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 2546609 ] | New: Support Request Workflow [ 3434268 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JRA workflow with restrictions [ 1647953 ] | New: GreenHopper Kanban Workflow 20141014 - Restricted [ 2546609 ] |
Workflow | Original: classic default workflow with restrictions [ 1518759 ] | New: JRA workflow with restrictions [ 1647953 ] |
Workflow | Original: classic default workflow [ 652323 ] | New: classic default workflow with restrictions [ 1518759 ] |
Workflow | Original: classic default workflow [ 32284 ] | New: classic default workflow [ 652323 ] |
Labels | New: severity-field |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Leslie,
It doesn't come preconfigured with JIRA (many people find the priority/severity distinction unnecessary and confusing), but issue severity can easily be added as a custom field. See:
http://jira.atlassian.com/browse/JRA-886
Cheers,
Jeff