-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.12.25, 11.3.11, 10.3.25
-
Component/s: Application Links, System Administration - Global Permissions
-
None
-
9.12
-
Severity 3 - Minor
Issue Summary
After setting up an Incoming, External, Application link to Jira with System Admin permissions, non-administrator accounts are unable to Manage Sprints even if the Token Scope is System Admin and they have the Manage Sprints permission
Steps to Reproduce
- Create an Application link in Jira
- External Application
- Incoming Application link Type
- Scopes = System Admin
- Setup an Oauth2 integration using the Key and Secret Provided
- Follow the Oauth2 authorization flow, and consent using an account that does not have System Admin permission, but does have the Manage Sprint permission
- Try to update a Sprint using API
Expected Results
The sprint is updated because the Token Endpoint Scope is System Admin and the consenting user has the Manage Sprint permission in Jira.
Actual Results
The Sprint Cannot be edited by the User and the error below is returned
{"errorMessages":["To update this sprint, you must either have the Manage Sprints or the Edit Sprints permission for all of the following projects: SCRUM."],"errors":{}}%
Workaround
Follow the Oauth2 authorization flow as an account that has System Admin Permissions
- relates to
-
JRASERVER-79519 Granular Permission Management for External, Incoming, Application Links to Jira
- Gathering Interest