Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Severity 2 - Major
-
Description
Summary
According to this documentation, in order to make an issue unassigned the name parameter in the request must be set to null.
Since we're deprecating this parameter and replacing it for accountId, it should work exactly the same as it did with name. However, when setting the accountId to null, the REST api call returns Bad request
Steps to replicate
- Create an issue and make sure that it's assigned to a user
- cUrl request:
curl -X PUT \ https://<instance_name>.atlassian.net/rest/api/3/issue/<issue_key> \ -H 'Authorization: Basic <basic>' \ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/json' \ -d '{ "accountId": null }'
Expected behavior:
- Should be able to update issue's assignee to unassigned.
Actual behavior:
- Bad request is returned:
{"errorMessages":[],"errors":{"assignee":"expected Object containing a 'name' property"}}
Additional details:
- Problem can be reproduced with both accountId and id
Attachments
Issue Links
- duplicates
-
JRACLOUD-69783 REST API /assignee does not set correctly when using accountId
- Closed