You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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)
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.