-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
7.1.0-OD-03, Archived Jira Cloud
-
7.01
-
1
-
Severity 1 - Critical
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
If you update the issue type scheme while removing an issue type you can get into a state where there is an option in the optionset that doesn't exist. This database corruption was the cause of JRA-45161. Fixing this would be removing another way to get into this state.
Steps to Reproduce
- Get an instance with an Issue Type Scheme with a set of Issue Types
- Current Option Set: [1, 2, 3], In the UI I change it to [1, 4, 2, 3]. Where these numbers represent Issue Types.
- During this processing, delete one of the Issue Types
- Check the database table optionconfiguration and there could be a possible row with an optionid that no longer exists.
- Until
JRA-45161is fixed this results in NPE in the UI.
Expected Results
Can create Issues like usual and the database table optionconfiguration should only have valid options.
Actual Results
Cannot create Issues or view workflows because of NPE and the database table optionconfiguration contains invalid options.
Workaround
This can be fixed by following the workaround in NullPointerException when creating issue, editing issue, move issue, accessing the Screen tab from the Project.
- Discovered while testing
-
JRASERVER-45161 Deleting an Issue Type can result in a NullPointerException when attempting to perform a number of actions within JIRA
- Closed
- relates to
-
JRACLOUD-61608 Inconsistent database state for Issue Type Scheme on Update and Remove
- Closed