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.
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:
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)
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..
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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