"Start work" unassigns issue

[Jason Brunette]

Jira and Bitbucket (Official) 2.1.0

Custom Jira site.

Steps to reproduce:

1. Open an issue you’re already assigned to and click “> Start work” button at top right.
2. Click the “Start” button at the bottom of the “Start work on Jira issue …” tab.
3. After processing, the issue is no longer assigned to me.

“History” of issue confirms “Assignee” being changed from me to a blank value.

‌

[Jason Brunette]

Attempting to “Start work” again leaves the issue unassigned as well.

[Pramod Busam]

@Jason Brunette Can you try remove the Jira site from the extension's settings screen and adding it again and see if that fixes the issue?

If not, could you try the following and let us know if you see any errors in the logs:

• In VS Code's settings (Preferences: Open Settings (UI) from command palette), search for curl and check the box for Atlascode: Enable Curl Logging
• In the same settings, page set Atlascode: Output Level to debug
• Open VS Code's output pane and select Atlassian from the dropdown. You should see the curl commands for the extension's network requests.

[Jason Brunette]

No errors, but I do see this which seems to indicate that the extension is specifically requesting the assignee be removed:

‌

[2019-10-17 13:11:14:858] curl -X GET -H "X-Atlassian-Token:no-check" -H "x-atlassian-force-account-id:true" -H "Content-Type:application/json" -H "Authorization:Basic <redacted>" "https://<redacted>/rest/api/2/myself"
[2019-10-17 13:11:14:858] ----------------------------------------------------------------------
[2019-10-17 13:11:15:155] ----------------------------------------------------------------------
[2019-10-17 13:11:15:155] curl -X PUT -H "Content-Type:application/json" -H "X-Atlassian-Token:no-check" -H "x-atlassian-force-account-id:true" -H "Authorization:Basic <redacted>" --data '{}' "https://<redacted>/rest/api/2/issue/2322332/assignee"
[2019-10-17 13:11:15:155] ----------------------------------------------------------------------
[2019-10-17 13:11:15:762] 
[2019-10-17 13:11:15:765] ----------------------------------------------------------------------

‌

When I run the curl command for the “myself” resource separately, I do get information about my account back:

‌

{"self":"https://<redacted>/rest/api/2/user?username=jb9244","key":"jb9244","name":"jb9244","emailAddress":"<redacted>","avatarUrls":{"48x48":"https://<redacted>/secure/useravatar?avatarId=10362","24x24":"https://<redacted>/secure/useravatar?size=small&avatarId=10362","16x16":"https://<redacted>/secure/useravatar?size=xsmall&avatarId=10362","32x32":"https://<redacted>/secure/useravatar?size=medium&avatarId=10362"},"displayName":"Brunette, Jason (jb9244)","active":true,"timeZone":"America/Chicago","locale":"en_US","groups":{"size":2,"items":[]},"applicationRoles":{"size":1,"items":[]},"expand":"groups,applicationRoles"}

‌

[Pramod Busam]

That is helpful. The request body must include the assignee id, but it is being sent as empty json (--data '{}'). We'll let you know once the fix is released.

[Pramod Busam]

Linked to VSCODE-805

[Nick Rundquist]

We just released version 2.1.3 of the extension which includes a fix for this issue.

[Alastair Wilkes]

Removing component: triaged (automated comment)