Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15668

Unnatural behavior of REST call: GET /rest/api/2/status

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • REST API
    • JRE 1.8.0_121, Rethat 7 (Linux 3.10.0-514.el7.x86_64)
    • 0
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The REST documentation for the upper call says:

      "Status 200 - application/json
      Returns a list of all JIRA issue statuses in JSON format, that are visible to the user."
       
      In detail this means only statuses are returned for projects, where the calling user has the permission "Browse Project". Statuses that are used with another workflow, that is used by another project only, will stay invisible to this user.
       
      But why can a full admin, who can add, modify and delete statuses (and see all, even non-associated in the UI) not receive the a full list of statuses with the upper call?
       
      At least, the REST documentation should be fixed to a wording like: "Returns a list of all JIRA issue statuses in JSON format, that are used by JIRA projects, that are visible to the user, regardless if normal user or administrator."

              Unassigned Unassigned
              8b31319ab581 Thomas Deiler
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: