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; } } }

Changing issue type schema without migrating old issues

Pier Nicolò

Hi everyone,

We would change the issue type schema in some of our projects, however, we do not want to migrate old issues to the new one.

The ideal scenario is to have the new issue types active in the project and the issues that we don't want to keep in, just "Inactive" or not available in the list during the "Creation" of a new ticket for the project.

I couldn't find any documentation about this except this guide, and I am not sure it might work out of the box:

https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784166/Issue+Type+Scheme+Migration

If someone has some idea about how to achieve this behavior it would be wonderful

Thanks ahead

Pier

Accepted answers

Dirk Ronsmans

Like @John Funk and @Nic Brough -Adaptavist- say, not possible to archive issue types.

I think the fastest/easiest solution might be to simply set up an "Archive" project, link the scheme to that one and move the issues over that have an issue type you no longer want.

Then you can create a new scheme and link that to the "live" project.

Just remove the "Create Issue" permission on that "Archive" project and you still have all your data to report on or to do a search for old data.

Might not be the cleanest but I feel it will definitely be the easiest and with the least amount of work/trickery

All comments

Nic Brough -Adaptavist-

It's not possible. An issue must be of a type that exists within the project.

There are a couple of tricks you can play to prevent creation of the "wrong" issue type, but you can't delete them from the project. (Scriptrunner's Behaviours can remove the option from the list, or you can put validators on the "create" transition that are impossible)

Pier Nicolò

Thanks @Nic Brough -Adaptavist- , we currently have Scriptrunner, I'll try to manage it in that way

John Funk

Hi Pier,

There is no concept of archiving issue types in Jira. You must migrate issues to an existing issue type if you plan to delete one of your issue types or remove it from the issue type scheme.

Dirk Ronsmans

Behaviours on Cloud might not be possible that's still being worked on I fear.

Dirk Ronsmans

Like @John Funk and @Nic Brough -Adaptavist- say, not possible to archive issue types.

I think the fastest/easiest solution might be to simply set up an "Archive" project, link the scheme to that one and move the issues over that have an issue type you no longer want.

Then you can create a new scheme and link that to the "live" project.

Just remove the "Create Issue" permission on that "Archive" project and you still have all your data to report on or to do a search for old data.

Might not be the cleanest but I feel it will definitely be the easiest and with the least amount of work/trickery

Pier Nicolò

Thanks @Dirk Ronsmans , I dunno why that option didn't come up to my mind, but it might be definitely another good option to keep the "Archive" concept available with a workaround.

Thanks for your help

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud