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; } } }

REST API documentation required scopes not found

KC Wong

Get issue property REST API (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-properties/#api-rest-api-3-issue-issueidorkey-properties-propertykey-get) states it requires either:

Classic - read:jira-work
Granular - read:issue.property:jira

But when I tried to create an organizational REST API token with scope, none of those can be found.

Accepted answers

Trudy P Claspill

Hello @KC Wong

Are you trying to create a token through https://admin.atlassian.com ?

If so are you trying to create it through Organization Settings > API Keys ?

That would not be the correct location. Those keys are only for accessing the Organization Admin API.

For the API you are trying to use you need a personal API token or a token created for a Service Account.

https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

https://support.atlassian.com/user-management/docs/understand-service-accounts/

All comments

Trudy P Claspill

Hello @KC Wong

Are you trying to create a token through https://admin.atlassian.com ?

If so are you trying to create it through Organization Settings > API Keys ?

That would not be the correct location. Those keys are only for accessing the Organization Admin API.

For the API you are trying to use you need a personal API token or a token created for a Service Account.

https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

https://support.atlassian.com/user-management/docs/understand-service-accounts/

Trudy P Claspill

Hello @KC Wong

I see that you accepted my answer.

Were you successful in creating the scoped API token for a service account or as a personal access token? And then successful in using that token with the API call?

KC Wong

Yes, I thought all types of tokens share the same list of scopes. I switched to use an OAuth2 token of a service account.

Now I need to figure out which scope allows me to use the overrideEditableFlag in Edit Issue REST API.

Johannes Seedorf (Isavren)

Hello KC Wong, regarding your question about overrideEditableFlag:

I do not believe there is a scope that enables it, so adding scopes to the service account will not help.

According to the Edit issue documentation, this flag is only available to Connect and Forge app users with the "Administer Jira" global permission (or to Forge apps acting on behalf of such users). What matters is the identity of the caller, not the scopes of the token. A service account using its own OAuth 2.0 credentials does not meet this requirement.

If a field is locked by the jira.issue.editable = false property on a status (such as "Done"), there are two common workarounds:

Transition the issue to an editable status, make the change, and then move it back to its original status, or
Add a dedicated (self-)transition to the workflow for such changes.

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-service-management-cloud

jira-service-management