nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Configuration query - Retire/Archive Issue type

Olle Friman

Hi Atlassian.

I am trying to find a way to retire an issue type, but do not succeed and would like your help to find a way to do this.

I have found this issue https://jira.atlassian.com/browse/JRA-26016 . But it does not help me much. As far as I can find there is no complete solution for this, but I saw somewhere that it might be possible to make some trick in the workflow.

Please let me know if you can help me with this.

Thanks

Olle

Accepted answers

Nic Brough -Adaptavist-

Yes, there is a slight weakness here - you can't remove an issue type without swapping existing issues of that type to one that will remain.

I've seen and tried/used a number of workarounds:

You could try javascript to get the users browser to prevent the users selecting the type. Good: consistent interface - the users simply aren't offered the option of that type. Bad: Pig to maintain, especially when Atlassian rearrange the interface on upgrade and it's a doddle to bypass, and if your javascript isn't strong (mine is awful), there's worries about it working on all browsers etc.

A more robust and blunt option is to reconfigure the issue type so that it behaves differently. There's two broad routes:

Add javascript to the "create" screen for the issue type - simply remove the "create" button (if it's a sub-task type, you'll have to think about the quick-add screen on parent issues as well). Again, a sneaky user can get around it, but it's more robust on upgrades and the code is easier.
Add something that breaks the issue creation - this is rock solid and can't be bypassed, but is quite annoying for users. To do it, I usually add a field called something like "do not let me work", then for the blocked issue-type, use the field configuration to make the field mandatory. Then, do not add it to any screen. Jira will demand the users enter it to create an issue, but they can't, so they can never commit a new issue.

I highly recommend telling your users if you use either of these blocking tricks - put something on screen saying "issue type not available, so don't bother". I use the Jira Toolkit message fields to do this (in big red letters etc)

All comments

unknown

One way is to do a search for that issue type, do a bulk edit and change the issue type to something else (turn your email notification off for that!). Then, just delete the issue type.

Nic Brough -Adaptavist-

Yes, there is a slight weakness here - you can't remove an issue type without swapping existing issues of that type to one that will remain.

I've seen and tried/used a number of workarounds:

A more robust and blunt option is to reconfigure the issue type so that it behaves differently. There's two broad routes:

Add javascript to the "create" screen for the issue type - simply remove the "create" button (if it's a sub-task type, you'll have to think about the quick-add screen on parent issues as well). Again, a sneaky user can get around it, but it's more robust on upgrades and the code is easier.
Add something that breaks the issue creation - this is rock solid and can't be bypassed, but is quite annoying for users. To do it, I usually add a field called something like "do not let me work", then for the blocked issue-type, use the field configuration to make the field mandatory. Then, do not add it to any screen. Jira will demand the users enter it to create an issue, but they can't, so they can never commit a new issue.

Srinivas Patrun

Hi Nic,

I followed your suggestion of hiding the unwanted issue type using JavaScript in JIRA 4.4.5 but it is not working on JIRA 5.2.5 because Create Issue and Create Subtask screens are now coming on dialog boxes. How could this be resolved in 5.2.5?

Nic Brough -Adaptavist-

Yes. In 5 and above, the javascript trick fails. I'm afraid your only real option now is the "break the create". Remove "summary" from the creation screen for that issue type. But please, if you do it like that, seriously chase up a way to put a message on the screen to tell the users that the issue type is deprecated!

Srinivas Patrun

I am not sure users will shout at that because till now we hide the issuetype(by using JS trick). We also have some other JS scripts that were pasted in the description of custom fields and they are working fine. Cant we get hold of issuetype option by any means to add this script..??? Please help..