Hi All,
I’ve run into an interesting problem this morning. The classic API scope: `read:servicedesk-request` seems to have disappeared when trying to generate a new scoped API token.
Additionally it looks like some of my old test tokens that were working based on that scope are no longer working.
I’ve mostly been able to get things working again using granular permissions. The main exception that I’ve seen so far is assets still seems borked, there are no granular scopes listed in the docs there either. I notice that there was a thread about that breaking last week, but no real resolution that I can see.
This is with a dev instance so there might be some oddities because of that.
Is there something I’m doing wrong or an update that I may have missed?
Thanks in advance!
@AnEvilPenguin Did you ever get a response or fix for this? I’m experiencing the same issue, and can’t find anything about those scopes being deprecated.
Hi @micahsmith
Radio silence unfortunately. I’ve been able to work around it in almost all cases with scopes. Luckily the cases where it’s not working (and no workaround) don’t seem to be that important to us. Thankfully everyone affected has been pretty understanding.
The weirdest case I found I needed to pull in some specific scopes from Jira not just JSM, we had do do the scoped read:user:jira and couldn’t just rely on read:jira-user (but only for JSM, still seems fine in Jira core).
Hopefully someone picks up the issue sooner rather than later. It was a scramble I could have done without!
1 Like
Good to know! Yeah I’ve resorted to using Granular scopes where needed, but it is a royal pain. And same deal here for read:user:jira. Seems odd they would deprecate those Classic scopes - especially given the fact they still reference them in their official API docs!
1 Like