-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
6.4.2, 6.4.4, 6.4.7, 6.4.8, 6.4.12, 6.4.14, 7.0.0-OD-02
-
6.04
-
19
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Issue summary
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
- Go to 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 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=""]}
Workarounds
- Create a new project
- Delete the issue type you no longer want
- Delete the issue type scheme if it is no longer needed
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
[JRASERVER-43097] Unable to delete issue type when no scheme is associated
Same error on JIRA 8.2.3. Is this bug resolving still planned or in progress?
Hello, veronique.blick! I'm afraid that Jira 6.4 reached End of life (please see our End of life policy) and it is no longer supported. What we can suggest is to upgrade to a supported version (currently 7.3) and verify if the issue persists. In case you require assistance with the upgrade procedure, experience issues with the upgrade itself, or the issue reported in this bug request is still present after the upgrade, please reach out to our Support team at https://support.atlassian.com/contact/
Best regards,
René Chiquete - Atlassian Support.
Veronique Blick
added a comment - We are also having this issue and the workaround is not working for us on Jira 6.4.7.
Is it possible to get some support? the issue is causing Jira to crash.
Veronique Blick
added a comment - We are also having this issue and the workaround is not working for us on Jira 6.4.7.
Is it possible to get some support? the issue is causing Jira to crash. 
Nicolas Forney
added a comment - Same error on JIRA 7.2.4. Is this bug going to be resolved in the near future?
Nicolas Forney
added a comment - Same error on JIRA 7.2.4. Is this bug going to be resolved in the near future? 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
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center