We have issue types we no longer need to use in active projects and would like to remove them from the Create Issue options while maintaining historical data in the project. What is the best way to stop users from creating new issues in this issue type while still using the project for other issue types?
There's no "retire" function.
Your only real options are to rename it to something to discourage users using it, move the issues out to another archive type project and remove the issue type from the project's issue type scheme, or put in validators that can't be passed.
You could use either, but a post-function won't give a message back to the user and it's quite hard to make one actually stop the transition. You need to deliberately code something that will crash rather than just fail - things like trying to update non-existent fields will just fail and carry on, rather than blocking the transition (You can tell I've been here before, right? ;-) )
We have added a validation rather than post-function, but that has the same problem that the user is not informed until after they have already entered (potentially a lot of) data.
Here's another option discussed:
Thank you everyone. The way we have managed this scenario to date is to rename the issue type as noted by Nic. Then we add a message to the create screen with info about the retirement and remove all other fields. We leave one of the removed fields as required so users are unable to complete the create function.
I was hoping there might be a better way now that we were unaware of.
Thank you all for your suggestions.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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