OAuth2 Permissions Issue with JIRA Service Management REST API

Question

Description:

We are experiencing an issue with the JIRA Service Management REST API where the OAuth2 permission with granular scopes seems to be insufficient. Specifically, we have checked the permission for read:incident:jira-service-management, but we are unable to use the following REST API due to authentication failures:

Issue Details:

* After granting the read:incident:jira-service-management scope, the REST API is returning an error indicating that authentication is unsuccessful.

Steps to Reproduce:

* Grant the read:incident:jira-service-management OAuth2 scope.
* Attempt to access the specific REST API endpoints mentioned above.

Justin _ ヨンス · Answer

@Matthias Gaiser _K15t_

Thank you for your response. I would like to ask a question from a different perspective. Is there a way to automatically add a team or members to the Responder Teams or Reponders(Edit Assts field attributes) when an issue is automatically cloned(In Jira Service Management)?

Matthias Gaiser (K15t) · Answer

I'm afraid I can't help much here then. :/

You can check out Atlassian's docs how to get help for building Forge apps. This also recommends asking your question in the developer community. Maybe you have more luck over there.

Justin _ ヨンス · Answer

I followed the instructions and used the script as described, but I encountered an issue. After getting the access token, the API request returns {"code":401,"message":"Unauthorized"}. Scopes like read:me work without any issues, but when I use read:incident:jira-service-management and write:incident:jira-service-management, I get this error after receiving the access token post-callback.

app-id: 15d03467-2f07-4cc2-884b-7354bca05045