Rest API shows Project Roles without scope for team-managed projects moved to trash

XMLWordPrintable

    • 6
    • Severity 3 - Minor
    • 8

      Issue Summary

      The REST API endpoints for getting project roles (/rest/api/3/role and /rest/api/3/role/{id})  don’t return the scope for deleted Team-managed projects that are in Trash.

      This makes it impossible to distinguish if a Project role belongs to a Company or a Team project and can later lead to errors when invoking other Jira APIs with such project roles (e.g. trying to create a permission scheme with a grant to such role with the API returns 400 - Bad Request, with error: “Please select a valid project role”)

      Steps to Reproduce

      1. Create a Next-Gen project and call one of the REST API endpoints to get project roles. See that project role scopes are returned in the response payload:
      2. Move the Next-gen project to the trash
      3. Call the same REST API endpoint(s) again

      Expected Results

      The APIs should either return the roles with scope or don’t return them at all (for the Next-gen projects in the trash).

      Actual Results

      The APIs return the project roles without scope, making them indistinguishable from roles for Company-managed projects.

       

      Workaround

      Remove the Nextgen Project from the Trash.

        1. When NG is deleted.png
          When NG is deleted.png
          346 kB
        2. When NG is in trash.png
          When NG is in trash.png
          352 kB

              Assignee:
              Unassigned
              Reporter:
              Sugandha Singh
              Votes:
              21 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: