When using Jira Scope Based Token, you need to set the following 15 permissions.
# | Scope | What It Covers |
1 | read:jira-work | Read issues, search (JQL), transitions, sprints, boards, backlogs, versions, filters |
2 | write:jira-work | Create/update issues, execute transitions, move issues to sprints/backlog, create versions, issue links |
3 | read:jira-user | Read user info (/myself, user search, user picker, group lookup) |
4 | manage:jira-project | Read projects, project statuses, create metadata |
5 | manage:jira-webhook | Create/manage webhooks for real-time sync |
6 | read:field:jira | Read custom fields (story points, dates, etc.) |
7 | read:issue-type:jira | Read issue types |
8 | read:issue-link-type:jira | Read dependency link types |
9 | read:board-scope:jira-software | Board operations (list boards, board config) |
10 | read:sprint:jira-software | Read sprints |
11 | write:sprint:jira-software | Move issues between sprints |
12 | read:epic:jira-software | Read epics |
13 | write:epic:jira-software | Update epics |
14 | delete:issue-link:jira | Delete issue links (dependency removal only — does NOT delete issues) |
15 | read:project:jira | Jira Project Details |
Create Scope Token in Jira
To make it easier to select the permissions, copy the following text and just paste that into the search area while creating token
read:jira-work
write:jira-work
read:jira-user
manage:jira-project
manage:jira-webhook
read:field:jira
read:issue-type:jira
read:issue-link-type:jira
read:board-scope:jira-software
read:sprint:jira-software
write:sprint:jira-software
read:epic:jira-software
write:epic:jira-software
delete:issue-link:jira
read:project:jira
Steps in Jira
Step : Add Token in Kendis
Return to the Add ALM Account modal in Kendis.
Enter:
Jira Login ID (Email).
Scope-Based API Token.
Note: Make sure that Using Scope API is enabled.
Click Test Connection.
If successful, your Jira Cloud Scope-Based connection is now established.