Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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.

Table of Contents

Checklist Permissions

...

In Issue Checklist

...

for Jira

Status
colourGreen
titleFREE
, users can see/edit the checklist if they can see/edit the issue.

...

In Issue Checklist for Jira

Status
colourPurple
titlePro
and
Status
colourBlue
titleenterprise
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 one 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 a the user has Edit issue permissions. Users with these permissions can:

Add Checklist Items Permission

Edit Checklist Items Permission

Toggle Checklist Items Permission

Delete Checklist Items Permission

Local Checklists

  • Add items

  • Add checklists

  • Load template in Append mode

  • Save checklist as a template

  • Change item summary

  • Change item description

  • Reorder items

  • Edit checklist name

  • Toggle items (complete / incomplete)

  • Change item status

  • Delete items

  • Delete checklists

  • *Load template in Overwrite mode

Global Checklists

N/A

N/A

  • Toggle items (complete / incomplete)

  • Change item status

N/A

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

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

Global View Checklist Permission

Permission

required to
Add checklist item

Permission required to

Edit checklist item

Permission

required to 
Toggle

checklist item

Permission

required to 
Delete

checklist item

Enabled – Local Checklists

Add Checklist Items

Edit Checklist Items

Toggle Checklist Items

Delete Checklist Items

**Disabled – Local Checklists

Company-managed / Classic projects:

Edit Issues

Edit Issues

Edit Issues

Edit Issues

**Disabled – Local Checklists

Team-managed / Next-gen projects

Member, Agent or

higher 

Administrator role

Member

or higher 

, Agent or Administrator role

Member, Agent or Administrator role

Member

or higher Member or higher 

, Agent or Administrator role

Enabled – Global Checklists

N/A

N/A

Toggle Checklist Items

N/A

**Disabled – Global Checklists

Company-managed / Classic projects:

N/A

N/A

Edit Issues

N/A

**Disabled – Global Checklists

Team-managed / Next-gen projects

N/A

N/A

Member, Agent or Administrator role

N/A

**Disabled is the only option for Issue Checklist Freefor Jira

Status
colourGreen
titlefree
, and the default option for Issue Checklist for Jira
Status
colourBlue
titlePro
and
Status
colourPurple
titleenterprise
.

Note

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.

...

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

    Image Added
  2. Click Edit Permissions under the Actions menu.

    Image Added
  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.)

    Image Added
  5. Click Grant.

    Image Added

For Team-managed/Next-gen Projects

...

nameCustomWorkChecklistNextGen

...

...

Click the Manage roles button (top right).

...

Click Create role and select the App permissions tab.

...

Give the new role a name.

...

Select the appropriate checklist permissions.

...

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

...

Click Create.

Understanding the Custom View Checklist Permission

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

Tip

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.

Note

If the Save local checklist data 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.

Global View Checklist Permission

Permission Required to View Checklist

Enabled

View Checklist

Disabled

This is the only option for Issue Checklist

Free

for Jira

Status
colourGreen
titlefree
, and the default option for Issue Checklist for Jira
Status
colourBlue
titlePro
and
Status
colourPurple
titleenterprise
.

  • Company-managed / Classic projects: Browse Projects

  • Team-managed / Next-gen projects: Viewer or higher role.

Tip

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

Using the Custom View Checklist Permission

...

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

    Image Added
  2. Click Edit Permissions under the Actions menu.

    Image Added
  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.).

    Image Added
  5. Click Grant.

For Team-managed/Next-gen Projects

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

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

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

    Image Added
  4. Give the new role a name.

  5. Select the View Checklist permission.

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

    Image Added
  7. Click Create.

Limit Ability to View/Edit Checklists to Assignee

...

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.

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

    Image Added
  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.

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

Template Permissions

Excerpt
nameTemplatePermissions

Understanding Template Permissions

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

Image Added

Note

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: 

Global custom Work on checklist permissionssetting  disabled

Global custom Work on checklist permissions setting enabled

See templates

Browse Projects

Browse Projects

Create template

Edit Issues

Add Manage Checklist ItemsTemplate

Load template (append)

Edit Issues

Add Checklist Items

Load template (overwrite)

Edit Issues

Add Checklist Items + Delete Checklist Items

Edit template (author)

Browse ProjectsBrowse Projects

Manage Checklist Template

Edit template (all)

Administer ProjectsAdminister Projects

Manage Checklist Template

Delete template (author)

Browse ProjectsBrowse Projects

Manage Checklist Template

Delete template (all)

Administer ProjectsAdminister Projects

Manage Checklist Template

Set default template

Administer ProjectsAdminister Projects

Manage Checklist Template

Team-managed (Next-Gen) Projects

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

Global custom Work on checklist permissionssetting  disabled

Global custom Work on checklist permissions setting enabled

See templates

Viewer, Member, Agent or higher Administrator role

Viewer, Member, Agent or higher Administrator role

Create template

"Member" , Agent or higher Administrator role

Add Create Checklist ItemsTemplate

Load template (append)

Member, Agent or higher Administrator role

Add Checklist Items

Load template (overwrite)

Member, Agent or higher Administrator role

Add Checklist Items + Delete Checklist Items

Edit template (author)

Viewer, Member, Agent or higher Administrator roleViewer or higher role

Manage Checklist Template

Edit template (all)

Administrator roleAdministrator role

Manage Checklist Template

Delete template (author)

Viewer, Member, Agent or higher Administrator roleViewer or higher role

Manage Checklist Template

Delete template (all)

Administrator roleAdministrator role

Manage Checklist Template

Set default template

Administrator roleAdministrator role

Manage Checklist Template

Tip

Note that in Team-managed (Next-Gen) projects, the default roles cannot be modified. In order to use custom permissions, you will need to create a custom role and grant the custom permissions to it.