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.
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/
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.