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)
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.