Restrict Issue Types for Jira

Documentation · Version 2.0 · English and French

Demo video

Silent demo with captions, recorded with sample data.

Overview

Restrict Issue Types lets project admins choose who can create each issue type in a Jira project, by group or project role. Restricted types are hidden from the Create dialog for everyone else. An optional workflow validator, added in one click, also refuses them when issues are created another way: REST API, CSV import or automation. Types without a rule stay open to everyone. Rules are stored in the project itself, and the app runs on Atlassian.

Getting started

After install, open Project settings > Apps > Restrict Issue Types. The page is shown to project admins and Jira admins.

  1. The page lists the project's issue types, each one open to everyone by default.
  2. Choose an issue type to restrict, for example Incident.
  3. Search your Jira groups and pick one or more, and add project roles if needed.
  4. If you are not in any of the chosen groups or roles, a warning tells you that you will no longer be able to create this type.
  5. Save. The Create dialog applies the rules the next time it opens.
  6. Optional: click "Turn on full protection" to add the app's validator to the Create transition of the project's workflows. This needs Jira admin rights. Without them, the page shows the manual steps to add the validator yourself.

For team members: the Create dialog only shows the types they may create. If the preselected type is not allowed, the first allowed type is selected. When full protection is on and they create a restricted issue another way, Jira refuses it with a message, in their language, asking them to contact a project admin.

Features

Permissions and data

Limits and what is not covered

FAQ

Support

See the support page or email support@assetguard.fr with your site URL, the app name and a screenshot.