nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Get Transitions in Jira Issues API is not working.

Dev Jadeja

I was trying out this API. OAuth 2 is used in our application. Request is failing with status code 403. We have all the scopes that API requires in our application too. Since that API can be accessed anonymously, I tried to hit it with Basic Auth with the same configuration and it is working for this way. What could be possibly going wrong when i am trying to access the API with Bearer Auth in OAuth 2?

Accepted answers

Caterina Curti

Thanks @Dev Jadeja for flagging this.

Your colleague shared this thread with us.
Let's move thist conversation to the post in the developer community: here: https://community.developer.atlassian.com/t/adding-readjira-scope-which-is-required-to-get-labels-is-causing-errors-in-other-apis/56311/9

Caterina

All comments

Martin Bayer _MoroSystems_ s_r_o__

Hi @Dev Jadeja welcome on the community. Did you check the scopes in Developer console?

https://developer.atlassian.com/console/myapps/

Dev Jadeja

Hi @Martin Bayer _MoroSystems_ s_r_o__, yes, these 3 scopes are already added there.

read:issue.transition:jira
read:status:jira
read:field-configuration:jira

Dev Jadeja

When I am trying to hit it with Bearer Auth Token in OAuth 2 using Postman, I am getting this message back with 403 as response code.

{
"errorMessages": [
"Access to the resource was denied due to missing scope grants. Your app was granted the following scopes: [write:webhook:jira, 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, delete:webhook:jira, read:issue:jira, read:project.component:jira, read:field.option:jira, api_access, read:group:jira, write:comment:jira, read:label:jira, read:issue-status:jira, write:comment.property:jira, read:issue-details:jira, read:issue-type-hierarchy:jira, read:jql:jira, read:user:jira, read:field:jira, read:issue-type:jira, read:project.property:jira, read:webhook:jira, read:field.default-value: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"
]
}

I also don't know why read:issue.transition:jira is not showing under the granted scopes section in the message above but I can assure you that read:issue.transition:jira scope is added in our OAuth 2 application.

Martin Bayer _MoroSystems_ s_r_o__

Hi @Dev Jadeja what if you remove the scopes and add them again?

Caterina Curti

Thanks @Dev Jadeja for flagging this.

Caterina

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud