-
Bug
-
Resolution: Timed out
-
Low
-
19
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
The user is unable to delete an issue type if there is no issue type scheme associated with the issue type.
Steps to reproduce:
- Delete issue type scheme that has issue types associated with it
- Goto issue type page
- Click delete on an issue type that has no issue type scheme associated with it
- Confirmation dialogue is displayed with no delete button; only cancel
Expected behavior
When the confirmation dialogue is displayed, there should be a delete button to confirm the delete action.
Actual behavior
There is only a cancel link displayed.
Error in jlog:
ERROR sysadmin 686x181x1 1c5djqp 131.103.28.240,59.167.29.217 /secure/admin/DeleteIssueType!default.jspa [webwork.util.ValueStack] query="matchingIssues/empty" {[id="matchingIssues" type="8" values=""]} {[id="empty" type="8" values=""]}
Confirmation dialogue:
Workaround:
- Create a new project
- Delete the issue type you no longer want
- Delete the issue type scheme if it is no longer needed
- is related to
-
-
- Gathering Impact
-
[JRACLOUD-43097] Unable to delete issue type when no scheme is associated
Is it all workaround?
Create a new project - done
Delete the issue type you no longer want - still see the same error!
The bug still alive in the second half of 2016, but the workaround works flawless
Morgan Thunder
added a comment - 2016 now...this bug still very much alive. 6.4.4 
Tony Zhang
added a comment - confirm this for us as well as 6.4.12 
Deleted Account (Inactive)
added a comment - I can confirm this issue for us, v6.4.7 
Jared Dohrman
added a comment -
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team