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

How can I prevent user from selecting a depreciated IssueType?

Pete P_lbwqsx

I have two service management projects that each contain the "Change" issue type. Both projects are still in use, one of the projects (ICC) contains the old "Change" issues that are depreciated. My users are fond of bypassing the customer portal and using the Jira "Create button" instead. I don't think I can remove the "Change" issue type from the issue type scheme if I have hundreds of issues without migrating them. What is the best way to deal with this?

Can I add some type of condition in the workflow of the ICC project that blocks creation of a specific IssueType. I only want users to create "Change" issues in the RFC project.

Accepted answers

Nic Brough -Adaptavist-

There are some tricks you can use, but none of them work perfectly.

As Ravi says, you can do some stuff with Behaviours to stop the UI offering people the issue type you don't want them to create. But it won't stop them changing the issue type with edit or move, it won't stop automations, scripts, post-functions, listeners, imports or external REST calls from creating them.

The other trick which will block everyone creating them (except import) is to have a separate workflow for that issue type, with an impossible validator on the create "transition" - something like "only allow this transition if the user can prove that 1 = 2"

But that still won't stop people moving issues from one type to the unwanted one.

Your only way that completely stops people using a defunct issue type is to remove it from the project, which means migrating issues of that type to another type.

All comments

Ravi Sagar _Sparxsys_

Hi @Pete P

Removing issue type from the scheme and migrating issues is the best option. If you have ScriptRunner for Jira then you can use Behaviours to hide that issue type. Using workflow validator can work but it is not a good user experience where the message is displayed after clicking a button to create the issue.

I hope it helps.

Ravi

Alexander Kravchuk_4zoa19

Hi @Pete P -- basically what Ravi said. The best way to go about it is to migrate all issues from one issue type to another. Other options could include adding validator to the "create" transition, adding some kind of automation rule to create "correct" change request and close original change request or removing all fields from "Create" screen for this issue type - but all of this is not the best UX. If you absolutely cannot migrate them to the new issue type, you can also consider introducing another project and moving them there for archival purposes and then decommission this issue type.

Nic Brough -Adaptavist-

There are some tricks you can use, but none of them work perfectly.

But that still won't stop people moving issues from one type to the unwanted one.

Your only way that completely stops people using a defunct issue type is to remove it from the project, which means migrating issues of that type to another type.

Pete P_lbwqsx

Thanks @Nic Brough -Adaptavist- , @Alexander Kravchuk & @Ravi Sagar _Sparxsys_ for all your suggestions and comments.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-server

workflow

jira-service-management

jira-service-management-server