You can create an new issue type and change all closed tickets(that linked issue types that you no longer use) via bulk change. all older tickets can be displayed with new issue type. Do not add this new issue type to any schema.
after, you can apply @Jack Brickey steps, so you can hide isssue type that you no longer use from drop-down field.
yes that little slight-of-hand would certainly work. :-) I would suggest you create a reusable issue type, e.g. "Hidden".
I was going to suggest trying Properties to limit the issue types but I'm unsure if this would work for Issue Type and the initial status (Open) or not but certainly worth a try. I have used for custom field drop downs just fine. There is some Atlassian documentation as well as a few Community examples of how to set up properties to limit drop down choices. If you do attempt and cannot figure it out I will try to assist further later today/tonight.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs