-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
4
-
It would be useful to define a global permission that would allow a user or group access to read ALL statuses via the API. Currently, only statuses that the calling user has access can be read via REST via the API calls
- GET /rest/api/2/status (returns a list of all statuses)
and/or - GET /rest/api/2/project/{projectIdOrKey}/statuses (returns all statuses in a certain project)
However, statuses are only returned that the user has permission to. This is defined by the "Browse Projects" permission.
Currently, a list of all statuses is only available by:
- Adding the calling user or group to each permission scheme (in an enterprise Jira environment, hundreds may be present, there therefore cumbersome to edit)
or - Directly read the statuses from the database using sql:
SELECT id, sequence, pname, description, iconurl, statuscategory FROM issuestatus;
- relates to
-
JSWSERVER-15668 Unnatural behavior of REST call: GET /rest/api/2/status
- Gathering Interest
Form Name |
---|
[JSWSERVER-20134] Add a global permission to read REST issue statuses
Support reference count | Original: 3 | New: 4 |
Support reference count | New: 3 |
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Link | New: This issue relates to JSWSERVER-15668 [ JSWSERVER-15668 ] |
Workflow | Original: JAC Suggestion Workflow [ 3286640 ] | New: JAC Suggestion Workflow 3 [ 3663573 ] |
Description |
Original:
It would be useful to define a global permission that would allow a user or group access to read ALL statuses via the API. Currently, only statuses that the calling user has access can be read via REST via the API calls
* [GET /rest/api/2/status|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns a list of all statuses) _and/or_ * [GET /rest/api/2/project/\{projectIdOrKey}/statuses|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns all statuses in a certain project) However, statuses are only returned that the user has permission to. This is defined by the "Browse Projects" permission. Currently, a list of all statuses is only available by: * Adding the calling user or group to each permission scheme (in an enterprise Jira environment, hundreds may be present, there therefore cumbersome to edit) __or__ * Directly read the statuses from the database using sql: {code:sql} SELECT id, sequence, pname, description, iconurl, statuscategory FROM issuestatus; {code} |
New:
It would be useful to define a global permission that would allow a user or group access to read ALL statuses via the API. Currently, only statuses that the calling user has access can be read via REST via the API calls
* [GET /rest/api/2/status|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns a list of all statuses) _and/or_ * [GET /rest/api/2/project/\{projectIdOrKey}/statuses|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns all statuses in a certain project) However, statuses are only returned that the user has permission to. This is defined by the "Browse Projects" permission. Currently, a list of all statuses is only available by: * Adding the calling user or group to each permission scheme (in an enterprise Jira environment, hundreds may be present, there therefore cumbersome to edit) _or_ * Directly read the statuses from the database using sql: {code:sql} SELECT id, sequence, pname, description, iconurl, statuscategory FROM issuestatus; {code} |
Description |
Original:
It would be useful to define a global permission that would allow a user or group access to read ALL statuses via the API. Currently, only statuses that the calling user has access can be read via REST via the API calls
* [GET /rest/api/2/status|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns a list of all statuses) _and/or_ * [GET /rest/api/2/project/\{projectIdOrKey}/statuses|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns all statuses in a certain project) However, statuses are only returned that the user has permission to. This is defined by the "Browse Projects" permission. Currently, a list of all statuses is only available by: * Adding the calling user or group to each permission scheme (the number of which could be quire large depending on the instance) __or__ * Directly read the statuses from the database using sql: {code:sql} SELECT id, sequence, pname, description, iconurl, statuscategory FROM issuestatus; {code} |
New:
It would be useful to define a global permission that would allow a user or group access to read ALL statuses via the API. Currently, only statuses that the calling user has access can be read via REST via the API calls
* [GET /rest/api/2/status|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns a list of all statuses) _and/or_ * [GET /rest/api/2/project/\{projectIdOrKey}/statuses|https://docs.atlassian.com/software/jira/docs/api/REST/latest] (returns all statuses in a certain project) However, statuses are only returned that the user has permission to. This is defined by the "Browse Projects" permission. Currently, a list of all statuses is only available by: * Adding the calling user or group to each permission scheme (in an enterprise Jira environment, hundreds may be present, there therefore cumbersome to edit) __or__ * Directly read the statuses from the database using sql: {code:sql} SELECT id, sequence, pname, description, iconurl, statuscategory FROM issuestatus; {code} |