Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Disable an issue type and keep issue with the disabled issue type

Looking to disable an issue type.  I don't want to convert already created issues to another issue type.  I want to restrict an issue type on the create page.


thank you


2 answers

1 vote

There are a couple of related questions about this. Some has some creative workarounds. The main crux of the issue is that there are no permissions for issue types.


Take a look at :


... and no "disable" functions.  If you want to remove an issue type from a project, you have to convert the issues of that type to another (or move them out of the project).  If you want to keep them, but stop people creating more, then, what Daniel said.

Hi @Nic Brough _Adaptavist_ , @Daniel Wester

We can stop User groups from creating the issues, But users can move issues to issue type.

Is there a way to stop moving issues to particular type. Thanks in Advance.

No, there's no way to do that.

Hi @Nic Brough _Adaptavist_ 

If I delete an issue type, is there any impact on the tickets created with that such issue type ?

Thanks in advance.


Yes, as above - you have to change them to an issue type that is not going to be removed.

Is there a feature request for this that I could vote for?

There have been several, but Atlassian shut them all down as "won't do", due to lack of interest.

Like Daniel Brvnišťan likes this

All you can do is to halt the ticket creation on the create screen. If you add a validator that always fails, will do the job.


I'd use a Field required validator that checks a built in filed that is not visible on the create screen becuase

- it is built in, not add-on supported so it won't pass when you uninstall an addon/the addon fails

- buil-in filed will not fail as it is not addon provided

- the Field required validator is able to display an error message like "This ticket type is not to be used"



- dirty

- ticket type is still selectable

- the user can lose time with filling the fields and then failing to create the ticket

- users can go around and move tickets to this ticket type


It is sad that Atlassian is not implementing this. Change management, retiring objects in JIRA is painful without handling Active/Obsolete/Disabled.

Suggest an answer

Log in or Sign up to answer