Hide issue types

Jira currently lacks an out-of-the-box solution for hiding issue types. To address this, we developed the Hide issue type rule, which works on the Create Issue screen. This feature allows you to hide specific issue types based on user roles, groups, or individual users—one of the most common use cases. But nothing stops you form setting preconditions based on other fields. For instance, you can display only Bug or Incident issue types if specific keywords are detected in the Summary field.

UIM does not support changing the visibility of issue type options on the Issue View.

Case 1. Hide obsolete issue types for all users, except those with the Administrator project role.

Restrict changing issue type

While it’s still possible to change the issue type on the Issue View, you can prevent this through Jira settings. Simply remove the issue type field from edit screens and update the permission schemes to revoke users' 'Move Issue' access.

Restricting issue creation using workflow validators

Another approach is to use workflow validators. While this method won’t hide issue types, it can prevent users from creating issues of a specific type. To achieve this, you’ll need an app that supports custom Jira expressions. Our team has developed the Jira Expression Validator, which is included in the Workflow Building Blocks for Jira app. You can use the following expression

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

There are several ways to implement this. If you're interested, visit our Jira Expression Library to explore more options and examples.