Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Add or remove restrictions on request types
The features described in this article are only available to those participating in the early access program (EAP) for restricting request types in Jira Service Management.
You may have request types in your company-managed service project that only specific people should be able to raise. These could be requests reserved for managers, different teams in your company, or even those managing sensitive information.
Control who has access to raise certain requests by restricting request types to give specific people access, and restrict access to all others. If a user doesn’t have access to a request type, they won’t be able to search or raise that request.
Restricted request types can be raised in all channels except email, chat, widget, and the virtual agent. Any request types being used by these channels will no longer appear to anyone regardless of access if restricted.
Add restrictions on a request type
From your service project, go to Project settings , and then Request types.
Select the request type you wish to restrict.
Select the lock icon ().
Add the users or groups you wish to give access.
Select Apply to save changes.
Remove restrictions on a request type
From your service project, go to Project settings , and then Request types.
Select the request type you wish remove restrictions on.
Select the lock icon ().
Select Remove next to the users or groups you no longer wish to have access.
Select Apply to save changes.
Only users and groups with Atlassian accounts can be given access to restricted request types. Project roles, customer accounts, and customer organizations are not supported at this time. Restrictions also apply to Jira admins and project admins who will still be able to configure restricted request types, but won’t be able to raise or preview them unless they grant themselves access.
These restrictions only apply to raising a request, and don’t extend to viewing an issue once it’s created. To add permissions around who can view issues, you’ll need to set up issue security levels.
Was this helpful?