-
Bug
-
Resolution: Cannot Reproduce
-
Medium (View bug fix roadmap)
-
None
-
6.4.2
-
6.04
-
The user is unable to create an issue after an issue type has been deleted. The Issue Type screens shows all the issue types as not being associated with an issue type scheme, however the issue type schemes are still present.
Steps to reproduce:
- Delete an issue type
- GET A 500 ERROR (not reproducible every time)
- Click delete on the issue type that was being deleted
- Get the below error with only a cancel button
Expected behavior
When clicking on the Create button, issue type drop down should be visible.
The default issue type scheme should not have double up issue types.
The issue types should all show as being associated with an issue type scheme.
Deleting an issue type should have a delete and cancel button present.
Actual behavior
(creating an issue) There is only a project drop down
(viewing issue type scheme) The default issue type scheme is showing two of most issue types (e.g. "Issue", and then "Issue" again)
(viewing issue types) All issue types are showing as not having any associated issue type scheme
(deleting an issue type) There is only a cancel link displayed.
Workaround:
- Open the Default Issue Type Scheme
- Click the Save button
- Everything returns to normal
- relates to
-
-
- Gathering Impact
-
[JRASERVER-43557] Issue Types all showing as not being associated with a Scheme after deleting an Issue Type
Hi jared.dohrman,
Index optimisation is off an removed from JIRA since JIRA 5.1.6 (see JRA-29487 for details). Consequently, I suspect that this is probably not an issue in modern versions of JIRA.
Please do let us know if you run into it ever again after upgrading your instance 
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Jared Dohrman
added a comment - Hi Oswaldo,
Try turning Index optimisation off, then edit 4 different issue types in separate tabs, then click delete on each of those 4 issue types simultaneously.
If this doesn't re-create the problem, then never mind.
Thanks,
Jared.
Jared Dohrman
added a comment - Hi Oswaldo,
Try turning Index optimisation off, then edit 4 different issue types in separate tabs, then click delete on each of those 4 issue types simultaneously.
If this doesn't re-create the problem, then never mind.
Thanks,
Jared. Hi jared.dohrman,
I have reviewed this again, and we need more information in order to be able to diagnose and find root cause for this issue in order for us to be able to schedule it and move it forwards.
If you are still suffering from this issue, could you please raise a support request with us at https://support.atlassian.com so we can investigate this in more detail? Thanks in advance
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Jared Dohrman
added a comment - Hi Matt,
I have not been game enough to reproduce as this was found in our Production environment.
When I encountered this, I was deleting a total of 4 issue types (that had been created as part of a JIRA Service desk new project set up). I deleted the first 3 issue types OK, but the 4th when deleted showed the scull and cross bones error.
Additional information that may be useful: We have Index Optimisation turned off (due to performance issues) so are assuming that the index was not written correctly whilst deleting the issue types.
The fix for us was to Edit the Default Issue Type Scheme and re-save it.
Thanks,
Jared.
Jared Dohrman
added a comment - Hi Matt,
I have not been game enough to reproduce as this was found in our Production environment.
When I encountered this, I was deleting a total of 4 issue types (that had been created as part of a JIRA Service desk new project set up). I deleted the first 3 issue types OK, but the 4th when deleted showed the scull and cross bones error.
Additional information that may be useful: We have Index Optimisation turned off (due to performance issues) so are assuming that the index was not written correctly whilst deleting the issue types.
The fix for us was to Edit the Default Issue Type Scheme and re-save it.
Thanks,
Jared. 
Thanks Oswaldo,
Will do
Thanks,
Jared.