-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
1
-
Severity 3 - Minor
-
1
Issue Summary
When using /rest/api/3/permissionscheme api for soft deleted team managed project the information about scope is missing
Steps to Reproduce
- Create team managed project
- Soft delete team managed project (use https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-projectidorkey-delete with enableUndo=true)
- query for permission schemes using https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-permission-schemes/#api-rest-api-3-permissionscheme-get
Expected Results
The permission scheme data for soft deleted team managed project should contain information about scope eg.
{
"expand": "permissions,user,group,projectRole,field,all",
"id": 10009,
"self": "https://atl-vertigo--jira-jira-branch-tkanafa--2.jira-dev.com/rest/api/3/permissionscheme/10009",
"name": "TES: Simplified Permission Scheme",
"scope": {
"type": "PROJECT",
"project": {
"id": "10005"
}
},
"permissions": [
Actual Results
the scope field/information is not present
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JRACLOUD-76117 Rest API shows Project Roles without scope for team-managed projects moved to trash
-
- Gathering Impact
-
-
JRACLOUD-80008 Display scope information of projects in trash in REST API response
- Closed
- duplicates
-
ACJIRA-2688 Loading...