Configure Permissions

New Feature Announcement

Global Checklists are currently in BETA and will be available in Issue Checklist for Jira ENTERPRISE once released. Contact our support team if you currently use Issue Checklist for Jira PRO would like to participate in the Beta.

By default, users who can view/edit the issue can view/edit the checklist. However, in Checklist for Jira Pro, you can configure custom checklist permissions that are independent of issue permissions.

Checklist Permissions

In Issue Checklist for Jira FREE , users can see/edit the checklist if they can see/edit the issue.

In Issue Checklist for Jira PRO and ENTERPRISE this is the default, however, you can choose to customize permissions to control who can  view, add, edit, toggle, and delete checklist items.

Understanding the Custom Work on Checklist Permission

The custom Work on Checklist permission can be used to control who can add, edit, toggle and delete items on local checklists, and who can toggle items on Global checklists, regardless of whether or not the user has Edit issue permissions. Users with these permissions can:

*Loading templates in Overwrite mode requires both Add Checklist Item permission and Delete Checklist Item permission.

Note that to access the checklist Editor, the user must be granted all of the permissions (Add, Edit, Toggle, Delete).

**Disabled is the only option for Issue Checklist for Jira FREE, and the default option for Issue Checklist for Jira PRO and ENTERPRISE.

For checklists to function properly, if the custom Work on checklist permission is enabled then the Checklist Text custom field must not be present on the Issue Edit and Issue Create screens.

Using Custom Work on Checklist Permissions

To enable Checklist custom permissions, log in as a Jira administrator and go to Jira Settings > Apps and select Permissions under the Checklist for Jira heading. Use the toggle to enable custom permissions for who can work on checklists.

This will render all checklists read-only until Project permissions have been configured.

For Company-managed/Classic Projects

1. After enabling the toggle, navigate to Project Settings > Permissions.

   

2. Click Edit Permissions under the Actions menu.

   

3. Navigate to the appropriate checklist permission (under issue permissions) and click Edit.

4. Select the appropriate role, application access or group. You can also click Show more to select users from the issue’s fields (Assignee, Reporter, etc.)

   

5. Click Grant.

   

For Team-managed/Next-gen Projects

Understanding the Custom View Checklist Permission

The custom View Checklist permission can be used to control who can see checklist and the checklist history. This configuration allows you to hide the checklist for users who still have access to the issue.

If a user is allowed to view the checklist but not edit it, the checklist will be displayed in read-only mode: all items will be visible but it won't be possible for the user to make any changes.

If the Save local checklist items to Jira custom fields setting is enabled and the Checklist Textfield is included on Jira screens, then the checklist content will be visible to users regardless of whether or not they have permission to view the list.

If the View Checklist custom permission is in use, and a user does not have this permission, they can still see assigned checklist items on Assigned checklist items page.

Using the Custom View Checklist Permission

To enable custom View Checklist permissions, log in as a Jira administrator and go to Jira Settings > Apps and select Permissions under the Checklist for Jira heading. Use the toggle to enable custom permissions for who can view checklists.

This will render the checklists invisible until Project permissions have been configured.

For Company-managed/Classic Projects

1. After enabling the toggle, navigate to Project Settings > Permissions.

   

2. Click Edit Permissions under the Actions menu.

   

3. Navigate to the View Checklist permission (under issue permissions) and click Edit.

4. Select the appropriate role, application access or group. You can also click Show more to select users from the issue’s fields (Assignee, Reporter, etc.).

   

5. Click Grant.

For Team-managed/Next-gen Projects

1. After enabling the toggle, navigate to Project Settings > Access.

   

2. Click the Manage roles button (top right).

   

3. Click Create role and select the App permissions tab.

   

4. Give the new role a name.

5. Select the View Checklist permission.

   

6. Select the users/groups who will be added to the role.

   

7. Click Create.

Limit Ability to View/Edit Checklists to Assignee

This can only be done with Company-managed (Classic) projects. Team-managed (Next-gen) projects do not currently support permissions for dynamic fields.

To allow only the assignee to view and/or work on checklists:

1. Log in as a Jira administrator and go to Jira Settings > Apps and select Permissions under the Checklist for Jira heading. Use the toggles to enable the custom Work on checklist and the custom View Checklist permissions.

   

2. After enabling the toggle, navigate to Project Settings > Permissions. Click Edit Permissions under the Actions menu.

   

3. Navigate to the appropriate permission and click Edit.

4. Click Show more on the Grant permissions popup.

5. Select Current Assignee and click Grant. Note that may also want to grant permission to the Reporter, Project lead, etc.

   

6. Remove permission from any Groups or Roles who should not be able to make changes to the checklist.

Template Permissions

Understanding Template Permissions

If the custom Work on Checklist Permission is enabled, the ability to create templates is granted by adding granting the appropriate user, role or group the Manage Checklist Template project permission in the project’s permission scheme.

Please note that similar to Jira, Issue Checklist allows System Administrators to perform actions that require Administer Project permission. 

Company-managed (Classic) Projects

The following permissions are required to work with templates in Company-managed projects: 

Team-managed (Next-Gen) Projects

The following permissions are required to work with templates in Team-managed projects: