Global Permissions
The global Permission page allows configuring permissions for various actions that users can perform with the app.
The page contains four groups of permissions
Template Permissions
Scope Permissions
Hierarchy Permissions
Checklist Permissions
Global Permission page is available only for the Jira administrators.
To open a Global Permission page:
Click on Templates on the navigation bar
Click on Permissions in the Configuration section.
Edit Permissions
Go to the Edit Permissions page:
Click on Templates in the navigation bar
Click on Permissions in the Configuration section.
Click Edit Permissions in the top right corner of the page
Click the Edit button for permission to be changed.
Permissions Dialog
Permission Dialog can contain four options depending on permission.
Option | Description |
---|---|
Anyone | Any user can perform this action |
Groups | Users in the listed groups can perform this action |
Users | Selected users can perform this action |
Owner* | The owner of the Template/Scope/Hierarchy can perform this action |
*Owner - optional
To mange groups or lists of users, you should have Browse Users Jira Permission
To successfully save permission, you should choose one or more suggested options. If the suggested option contains an additional field, the field must be filled.
Template Permissions
To set permissions for Templates, choose necessary permission in a Templates Permission table and click Edit.
Create Templates
The user that has this permission can create new Templates.
Edit Templates
The user who has this permission can edit Templates that are available for him in Jira, except in the case when the permission option is set to the Owner, which only allows editing Templates created by the user.
You can extend a list of Templates that the user can see on the Manage Templates page by setting “View all Templates” permission for the user.
Delete Templates
The user who has this permission can delete Templates that are available for him in Jira, except in the case when the permission option is set to the Owner, which only allows deleting Templates created by the user.
You can extend a list of Templates that the user can see on the Manage Templates page, by setting “View all Templates” permission for the user.
Change Template Owner
The user granted this permission is able to change the Owner of the Templates.
View All Templates
This permission controls a list of Templates that will be displayed to the user on the Manage Templates Page.
The user that doesn’t have this permission can only view his own Templates and Templates that are available in projects accessible for the user that correspond to his Scope.
Apply Templates
The user granted this permission can apply Templates using the API. The Template is applied by its ID for the same issue type and project in which it was created. You can find the additional information about the Templates API via the link.
For example, if the ‘Smart’ Template with the ‘50’ ID was created using the ‘Scrum Software Development’ project and the story as the issue type, applying this template will create the story in the ‘Scrum Software Development’ project containing the 'Smart’ Template fields values.
Scope Permissions
To set permissions to Scopes, choose necessary permission in a Scope Permissions table and click Edit.
Create Scopes
The user that has this permission can create new Scopes.
Edit Scopes
The user that has this permission can edit any available Scope, except the case when the permission option is set to the Owner, which only allows editing Scopes created by the user.
Delete Scopes
The user that has this permission can delete any available Scope, except the case when the permission option is set to the Owner, which only allows deleting Scopes created by the user.
View All Scopes
This permission controls a list of Scopes that will be displayed to the User on the Manage Scopes Page.
The user that doesn’t have this permission can only see his own Scopes and Scopes that are available for the group the current user belongs to.
Hierarchy Permissions
Create Hierarchies
The user that has this permission can create a new Hierarchy.
Edit Hierarchies
The user that has this permission can edit any available Hierarchy, except the case when the permission option is set to the Owner, which only allows editing Hierarchies created by the user.
Delete Hierarchies
The user that has permission can delete any available Hierarchy, except the case when the permission option is set to the Owner, which only allows deleting Hierarchies created by the user.
Apply Hierarchies
The user that has this permission can apply Hierarchies.
Setup Scheduler
The user that has this permission can set up a scheduler in Hierarchies.
Checklist Permissions
Manage Checklists
The Manage Checklists permission granted to the user gives the opportunity to create, edit, delete, view the checklists and view the checklists' scopes on the Manage Checklists page. Having this permission enables the adding and removing the checklists to the specific hierarchies on the Manage Hierarchies page.
If the user doesn’t have the Manage Checklists permission granted the Checklists functionality is not available for him.
The checklists that are available for the current user by the Available for field value on the Create Checklist dialog are displayed on the Issue view page after the hierarchy apply.
Restore Default Permission Schema
To restore the Default Permission Schema go to the Edit Permissions page:
Click on Templates on the navigation bar.
Click on Permissions in the Configuration section.
Click Edit Permissions in the top right corner of the page.
Сlick on Restore default in the top right corner of the page.
Click the Confirm button in Confirmation dialog.
Permissions advantages the jira-administrators group members are granted by default
To simplify the Smart Issue Templates app management the members of the jira-administrators group are granted the main permissions by default. In case they are not granted the specific Smart Issue Templates permissions, admins are able to execute some actions.
As for the Templates permissions admins can edit the templates, change the template owner and delete templates.
As for the Scopes permissions admins are able to view all scopes.
As for the Hierarchies permissions admins are able to apply, edit and delete the hierarchies.
As for the Checklists permissions admins don’t have any advantages.