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.
- The page lists the project's issue types, each one open to everyone by default.
- Choose an issue type to restrict, for example Incident.
- Search your Jira groups and pick one or more, and add project roles if needed.
- 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.
- Save. The Create dialog applies the rules the next time it opens.
- 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
- One rule per issue type: everyone, or only some groups and project roles.
- Rules use group ids, so renaming a group does not change a rule.
- Warning when an admin would lock themselves out of a type.
- A type cannot be saved as restricted to nobody.
- Restricted types hidden in the Create dialog.
- Workflow validator that also blocks the REST API, imports and automation, turned on in one click. It does not change the workflow's other rules.
- Works in company-managed and team-managed projects.
- Light and dark themes, English and French.
Permissions and data
- The app runs on Atlassian's Forge platform (Runs on Atlassian). It uses no external servers.
- Rules can only be changed after the app checks that the person is a project admin or Jira admin. Changes run with the permissions of the admin changing the rules (asUser).
- The UI modification that filters the Create dialog is created by the app (asApp), after checking that the person is a project or Jira admin. The UI modification and the validator only hide or block issue types.
- read:jira-work: read the project's issue types and the rules stored in a project property, so the settings page and the Create dialog know which types to show.
- read:jira-user: read the current user's groups and project roles, and search group names in the rule editor.
- manage:jira-project: save the project's rules as a project property and manage the project's UI modification that hides restricted types in the Create dialog.
- manage:jira-configuration: when a Jira admin clicks "Turn on full protection", add the app's validator to the Create transition of the project's workflows.
- write:app-data:jira: lets the app create and remove the project's UI modification.
- Rules store group and role ids only. No data leaves your Atlassian site.
Limits and what is not covered
- Without full protection, restricted types are only hidden in the Create dialog. Other ways of creating issues are blocked only once the validator is on the Create transition.
- Full protection needs Jira admin rights, or adding the validator to the Create transition yourself.
- Not covered: changing the type of an existing issue and moving an existing issue, the Jira Service Management customer portal and agent view, a site-wide report of who can create what.
FAQ
- Where is the app? Project settings > Apps > Restrict Issue Types.
- Do I need to be a Jira admin? No. Project admins can set the rules. Turning on full protection in one click needs Jira admin rights.
- What happens to types without a rule? They stay open to everyone.
- What if a group is renamed? Nothing changes. Rules use group ids, not names.
- Can I lock myself out? The page warns you before saving if you are not in any of the chosen groups or roles.
- Someone created a restricted issue through the API or an import. Turn on full protection so the validator refuses it.
Support
See the support page or email support@assetguard.fr with your site URL, the app name and a screenshot.