-
Type:
Suggestion
-
Resolution: Timed out
-
2
-
2
Issue Summary
Performing a request to the Get screens REST API endpoint, the response contains the scope information of the project if it's available. In case the project is moved to the trash, the scope information does not appear, however the screen is still available. Therefore, in this feature request, it would be valuable to have the information of having scope even when the project is in the trash.
Steps to Reproduce
- Perform the request for the REST API endpoint: GET /rest/api/3/screens.
- Notice the scope information for the project.
- In case the project is deleted, the scope will not appear in the response of the endpoint.
Expected Results
The scope information to be available even after the project is in trash.
{
2 "id": 10000,
3 "name": "TEST: Simple Default Issue Screen",
4 "description": "",
5 "scope": {
6 "type": "PROJECT",
7 "project": {
8 "id": "10000"
9 }
10 }
11},
Actual Results
There's no scope information available for the project in trash.
{
2 "id": 10000,
3 "name": "TEST: Simple Default Issue Screen",
4 "description": ""
5}
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-81518 when using Get all permission schemes endpoint no information about scope is returned for permission schemes for soft deleted team managed projects
-
- Closed
-
- relates to
-
JRACLOUD-76117 Rest API shows Project Roles without scope for team-managed projects moved to trash
-
- Gathering Impact
-