-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
None
-
Affects Version/s: 4.2
-
Component/s: None
-
4.02
As per the summary. refreshing the Issue Types page, reindexing.. all does not help. Only restarting Jira re-sorts the issue types out in alphabitical order again after an issue type is renamed.
- duplicates
-
JRASERVER-23196 Renaming Priority, Resolution, Status, Issue Type does not get reflected until a system restart
-
- Closed
-