Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to unassign issue using Bitbucket's Rest API?

bdbowen July 15, 2021

I have had success assigning issues through Bitbucket's Rest API. I just set the value assignee with an array containing the uuid of the individual (alternatively using account_id also works). However, I have not had success with unassigning issues using the Rest API. I have tried numerous things:

Saving Issue without any assignee value (essentially undefined, it isn't set). This results in saving the issue successfully, but retaining the assignee value from before (since it wasn't changed).

All other ways that I have tried have resulted in the error: "Bad request: Key 'assignee' None is not a collaborator on this repository." These are some of the things that I have tried:

'assignee' => null

'assignee' => ['name' => null]

'assignee' => ['uuid' => null]

'assignee' => ['account_id' => null]

'assignee' => ['username' => null]

'assignee' => ['name' => null, 'username' => null, 'account_id' => null]

Can anyone tell me what I am missing?

1 answer

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 23, 2022

G'day!

When you are using JIRA, a user which has not yet been assigned is known as "Unassigned". Are you able to try using "Unassigned" instead of "null" and let me know how this goes? 

Cheers!

- Ben (Bitbucket Cloud Support)

Z
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 14, 2022

Hi @Ben 

This did not work - I have tried setting assignee to:

0
''
null
false
'null'
'None'
'Unassigned'
'unset'

All of them return the same error:

{"type": "error", "error": {"message": "Bad request", "fields": {"assignee": "None is not a collaborator on this repository"}}}

This is the endpoint: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-issue-tracker/#api-repositories-workspace-repo-slug-issues-issue-id-put

Everything else works as expected - its just assignee that doesnt work

Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 14, 2022

Hey @Z 

Upon further testing it appears you are correct - when performing a GET request on an issue it shows "assignee: null" in the HTTP response so it only makes sense that the same JSON argument should be able to be parsed using the PUT method.

I have raised a formal bug ticket with our developers. Feel free to "Watch" this issue for future updates:

https://jira.atlassian.com/browse/BCLOUD-22021

Cheers!

- Ben (Bitbucket Cloud Support)

Like Z likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events