Issue Summary

The REST API for project roles has an inconsistency between the GET and DELETE endpoints when handling project-scoped roles (roles originating from team-managed projects).

• GET /rest/api/3/role returns project-scoped roles (Project roles from Team managed projects)

• DELETE /rest/api/3/role/{id} does not support deleting these project-scoped roles, resulting in an error

Steps to Reproduce

1. Have a Jira Cloud instance where team-managed projects with custom project roles were previously created.
2. Call GET /rest/api/3/role — observe that project-scoped roles are returned in the response
3. Attempt to delete one of these roles via DELETE /rest/api/3/role/{id}
4. Observe that the DELETE call fails / does not delete the project-scoped role

Expected Results

• Either the DELETE endpoint should support deleting project-scoped roles, OR

• The GET endpoint should not return project-scoped roles that are no longer actionable (orphaned), OR

• Documentation should clearly state the limitation

Actual Results

GET returns project-scoped roles, but DELETE cannot remove them — creating an inconsistency.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available