Details
Description
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."
Attachments
Issue Links
- is related to
-
JSWSERVER-20134 Add a global permission to read REST issue statuses
- Gathering Interest