Is there a way to remove/hide an issue type without migrating existing JIRAs

[Daniel Ng]

I am sure this has been brought up before but I want to remove a few issue types from a project.

But removing he issue type will require me to convert existing JIRAs of that issue type to another active issue type.

I heard there are some people that use scriptrunner to hide the issue type.

But wondering if someone has got a simpler solution.

[Kristian Walker _Adaptavist_]

Hi Daniel,

If you have ScriptRunner for Jira Cloud installed, you can achieve this requirement using the behaviours feature.

As mentioned in the documentation page here, behaviours support the Issue Type field on the Create View screen for company-managed projects.

Using this, you could limit what issue types are displayed when an issue is created using the setOptionsVisibility() method and passing the ID's of the issue types that should be shown, and we have an example of how to do this here as a reference.

I hope this information helps.

Regards,

Kristian

[Maciej Dudziak _Forgappify_]

Hi @Daniel Ng

Currently, Jira does not offer an out-of-the-box solution for this. However, if you're open to using apps and prefer a straightforward approach, our team has developed Field Rules for Jira, which includes a Hide Issue Type rule that works on the Create Issue screen. With just a few simple steps, you can hide specific issue types based on a user's project roles, groups, or for individual users.

Another approach would be to use validators. While this won't hide issue types, it can prevent users from creating issues of a certain type. To implement this, you would need an app that allows you to write custom Jira expressions. There are several options available on the Atlassian marketplace.

I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira app. Expression you can use is as follows:

user.getProjectRoles(issue.project).reduce(
  (isAllowed, role) => isAllowed || ["Developers"].includes(role.name),
  false
)

There are many ways to implement this, if you are interested I am leaving link to our Jira expression library.

I hope it will help.

Cheers

[Tomislav Tobijas _Koios_]

Hi @Daniel Ng ,

For these kinds of requests, we usually implement ScriptRunner and use app functionalities to do so. However, you could potentially configure Jira validators (I'm not sure if we ever used native ones) on create issue transition to get this to work.

Apart from that, here's a feature request regarding this requirement: JRACLOUD-44557: Restrict creation of issues based on issue type 

Cheers,
Tom