-
Bug
-
Resolution: Invalid
-
Low
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
As described here, a new REST API call was introduced in JIRA 7.0 that returns the value of the property with a given key from the user identified by the key or by the id. However, it's always returning Error 404.
Expected behaviour
Returns the value of the property with a given key from the user identified by the key or by the id.
Actual behaviour
Error 404 is returned, which means user with given key or id does not exist or if the property with given key is not found.
Example
Call
<instance url>/rest/api/2/user/properties/<propertyKey>?username=<user>
Response
{"errorMessages":["The property <propertyKey> does not exist."],"errors":{}}
Steps to Reproduce
- Add a key-value pair under properties on <instance url>/secure/admin/user/EditUserProperties.jspa?name=<user>;
- Try to list the property value of the key for this user with the below REST API call;
http://<jira-url>/rest/api/2/user/properties/<property key>?userKey=<user>
- Observe the response returned is code 404;
Workaround
At this point, there's no workaround for obtaining users' properties using a REST API call.
- is related to
-
JRACLOUD-45502 Response of GET /rest/api/2/user/properties always empty
- Closed
-
JRASERVER-59760 GET /rest/api/2/user/properties/{propertyKey} Returns Error 404
- Closed
-
JRACLOUD-60326 Update Rest API documentation to clarify about /rest/api/2/user/properties/{propertyKey}
- Closed
- relates to
-
JRACLOUD-72660 Searching for users with a certain property via REST API returns empty string
- Closed
- is resolved by
-
CRANE-2353 Loading...
-
DXD-435 Loading...