Jira REST API - GET transitions (issue/issueIdOrKey/transitions) Fails due to new scope changes

The API GET transitions fails with the error:

“Access to the resource was denied due to missing scope grants. Your app was granted the following scopes: [read:status:jira, read:application-role:jira, write:attachment:jira, read:project-category:jira, read:project:jira, read:issue.vote:jira, read:field-configuration:jira, write:issue:jira, read:issue-security-level:jira, write:issue.property:jira, read:issue.changelog:jira, read:avatar:jira, read:issue-meta:jira, read:issue:jira, read:project.component:jira, api_access, read:group:jira, write:comment:jira, read:issue-status:jira, read:priority:jira, write:comment.property:jira, read:issue-type-hierarchy:jira, read:user:jira, read:issue-type:jira, read:project.property:jira, read:project-version:jira].\nThe resource can be accessed by having one of these groups of:\n * current scopes: [read:status:jira, read:issue.transition:jira, read:field-configuration:jira]\n * deprecated scopes: [read:jira-work]\n”

Currently, we configured 3LO app with below scopes:

Here’s the request(CURL) that we have made, stripped down the token:

curl --location --request GET ‘https://api.atlassian.com/ex/jira/<cloud_id>/rest/api/3/issue/GTP/transitions’ --header 'Authorization: Bearer ’ --header ‘Accept: application/json’ --header ‘Content-Type: application/json’ --header ‘Connection: keep-alive’ --data-raw ‘’

Here’s the response that we got:

{“errorMessages”:[“Access to the resource was denied due to missing scope grants. Your app was granted the following scopes: [read:status:jira, read:application-role:jira, write:attachment:jira, read:project-category:jira, read:project:jira, read:issue.vote:jira, read:field-configuration:jira, write:issue:jira, read:issue-security-level:jira, write:issue.property:jira, read:issue.changelog:jira, read:avatar:jira, read:issue-meta:jira, read:issue:jira, read:project.component:jira, api_access, read:group:jira, write:comment:jira, read:issue-status:jira, read:priority:jira, write:comment.property:jira, read:issue-type-hierarchy:jira, read:user:jira, read:issue-type:jira, read:project.property:jira, read:project-version:jira].\nThe resource can be accessed by having one of these groups of:\n * current scopes: [read:status:jira, read:issue.transition:jira, read:field-configuration:jira]\n * deprecated scopes: [read:jira-work]\n”]}

If you look at the above Response doesn’t reflect the actual permissions set in the application or the ones that is used during Application authorization, it had replaced one of the permissions (read:issue.transition:jira) that we have set with api_access or it was getting removed.

We have all the necessary scopes(permissions) configured in the application and we used the same during initial authorization as well. But while retrieving(get transition) transitions, we are getting the above mentioned error, whereas we are able to access all the other APIs, without any problem.

The same issue can also be present in transition POST API as well, though we haven’t tried that yet. Also all these issues started appearing after the latest changes in the JIRA and we have been noticing the issue for last few days.

2 Likes

Hi @ChandraMohan, there issue around read:issue.transition:jira was recently fixed, please let us know if you still experience issues when contacting the /transitions endpoint. :slight_smile:

2 Likes