-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.9.2, 7.7.4, 7.8.4
-
None
-
7.07
-
5
-
Severity 2 - Major
-
4
-
Summary
Before Jira 7.6, it was possible to mark a priority as Default so that when users create new issues, Jira will pick that Default priority.
After 7.6 and the introduction of Priority Schemes, it is not possible to mark a priority as 'default' under Default Priority Scheme.
Next to that, when upgrading from pre 7.6 release to post 7.6 release, if there was a default priority set, then it is lost now.
Steps to Reproduce
- Set up a Jira instance on 7.5
- Set a particular priority as default
- Upgrade to Jira 7.7
- Notice that the default priority is now lost. So when users create an issue, Jira might start picking up a different default priority and there is no way to change this.
Expected Results
Jira should continue to use the old default priority and even provide means to change it.
Actual Results
The default priority may have changed and there is no way to change it.
- is related to
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
-
JRASERVER-66660 Provide the ability to edit the default priority scheme
- Future Consideration
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-