You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have an issue type (Email Deployment) that I no longer want to have as an option in my Workflow Scheme. I see in the Settings/Workflow Schemes that I can simply 'edit' and then delete that issue type, but my question is what happens to those previously created tickets (Email Deployment)? Will they remain or be deleted?
I want them to remain, I just don't want hat issue type as an option for new ticket types moving forward.
When you delete an issue type from a Workflow scheme, you're really removing that issue type's association with a specific workflow spelled out in that scheme. That issue type will then be associated with the workflow set aside for all Unmapped Issue Types.
What you're looking to do is remove the issue type from the project's Issue Type Schemes. Jira will then prompt you to remap the existing issues to a different issue type.
Hi @Angela,
The issues won't be deleted. But Jira will detect that there are issues of the specific type in your project and will ask you to migrate them to a different issue type in your project (you cannot have issues in a project of a type that is no longer there).
That may have some additional implications: changing the issue type may also result in the workflow and screens of your issues to change. Again, Jira will alert you and ask you to decide what you want to do there (convert olld workflow statuses into new ones, potentially remove data from certain custom fields that are not on the screens of the new issue type).
In this scenario: prepare. Have a look at the differences in configuration between your current issue types and make sure you know how you want to convert your old issues.
As an alternative, you can also move your old issues to a different project (or different issue type in your current project first) before you remove the old type from your issue type scheme.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Angela, another approach is to set up a workflow that has a very restrictive validator on the Create transition, so that no one can create issues, and then assign that workflow to the Email Deployment issue type in the Workflow Scheme for the project. That way the existing tickets will live on, but no new tickets can be created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.