To fetch priority schemes, the documentation says that “read:priority-scheme:jira” is the required granular permission. However, I am not seeing this listed as an option when assigning scopes to API tokens.
2 Likes
Hi @DX1
For this kind of permission, you need to add it in your manifest:
permissions:
scopes:
- ‘read:jira-work’
- ‘read:priority-scheme:jira’
This scope does not appear as an assignable option when creating a regular API token.
This is expected.
Those granular permissions (read:priority-scheme:jira, read:field-configuration:jira, etc.) are not supported when using the standard UI API Tokens.
You say “This is expected.” Why? Why would it not be supported on standard UI for API token creation?
Since these are granular scopes, they are only usable in your app manifest (or via OAuth 2.0 with fine-grained permissions), you cannot assign them via the standard API token UI.
You just have to add it in your manifest, and everything work.
I would understand that, except this doesn’t seem to be the case for other endpoints. The (now-deprecated) /priority endpoint mentions read:priority:jira, which IS available in the UI dropdown (see screenshot in my original post). Same with another endpoint we use, /project/search. It lists a bunch of granular scopes, including read:issue-type:jira, read:project:jira, read:project.property:jira, which are all available in the UI dropdown. I hope you can understand where my confusion is coming from.
I understand very well the confusion, it’s not easy ti get it.
By adding it to your manifest, your problem is solved ?
It’s not, there is no manifest. We’re not using a Forge app.
Sorry to butt in….
@DX1 Yes, the Granular scope read:priority-scheme:jira is not available for you to add via the GUI.
The reason is simpler than you think; the Priority Schemes endpoints are very new and still experimental, so their granular scopes might change, and the GUI for choosing what scopes to add to a token is yet to ‘catch up’ with this situation… hence the reason none of the *.priority-scheme.jira Granular scopes are available to add.
So, since you currently can’t add that required Granular scope via the GUI, just add the Classic scope manage:jira-configuration which should available. Just be careful how you use that API token, as having permission to broadly manage Jira’s configuration is dangerous!
Got it, thanks for that context. Do you have any idea when the GUI will “catch up”?
Nope.
Looks like it’s been already reported as a bug in JRACLOUD-96390. I’ve added a comment about essentially the same problem happening when trying to add those Granular scopes via the GUI. Add your vote!
After doing some more research, those REST API endpoints were part of the rollout of the general Priority Schemes feature release that originated in Feature Request JRACLOUD-3821 (boy, didn’t that one take a long time to get over the line! Only 5,631 votes over 20 years.) and the REST API endpoints were announced in CHANGE-1603 in May 2024, so they are not new, but about a year and a half old, so the problem you’ve encountered is just as old 
I guess I’m lucky, ‘cause I’ve never had to use those API endpoints.
Amazing. Thanks for your help here sunnyape
1 Like