Error when creating branch from jira view

Issue #466 new
Ilya Valmianski created an issue

From vscode/jira view if I click on “start work” it allows me to create a branch on a linked Bitbucket (both Jira and Bitbucket are hosted on prem and I am correctly authenticated). However, after the branch creation I get the following error message:

Something went wrong

config:``{"data":"{\"name\":\"ilyav\"}","headers":{"Accept":"application/json, text/plain, */*","Accept-Encoding":"gzip, deflate","Authorization":"Basic ***","User-Agent":"axios/0.19.0","X-Atlassian-Token":"no-check","x-atlassian-force-account-id":"true"},"maxContentLength":-1,"method":"put","timeout":30000,"transformRequest":[null],"transformResponse":[null],"url":"``https://***/rest/api/2/issue/24420/assignee","xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN``"}

message:``"Request failed with status code 405"

name:``"Error"

stack:``"Error: Request failed with status code 405\n\tat e.exports (/users/m673946a/.vscode-server/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:581608)\n\tat e.exports (/users/m673946a/.vscode-server/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:912586)\n\tat Unzip.<anonymous> (/users/m673946a/.vscode-server/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:1699518)\n\tat Unzip.emit (events.js:205:15)\n\tat endReadableNT (_stream_readable.js:1154:12)\n\tat processTicksAndRejections (internal/process/task_queues.js:84:9)"

Nonetheless, the branch really does get created on Bitbucket and local working directory is correctly switched to the new branch so not sure what exactly is errored.

This happens every time I try to click “start work”.

I am running “Jira and Bitbucket (Official)” plugin version 2.4.9 on a remote RHEL 7.5 server (via SSH) from vscode (1.41.1) running on MacOSX 10.14.6. Our on prem Jira is Jira v7.12.1. Not sure about Bitbucket but I guess it was bought on the same license.

Comments (6)

  1. Pramod Busam Account Deactivated

    @Ilya Valmianski The extension tries to assign the Jira issue to you as part of the start work action and looks like that bit is failing. Could you update to the latest version of VS Code and ensure you have the latest version of the extension (2.7.0 or later) and let us know if this is still an issue? (We have updated the minimum version of VS Code supported for some of the recent versions of the extension.)

  2. Ilya Valmianski reporter

    Just updated to vscode 1.48 and extention 2.7.0. Same error except now much less verbose, just says

    Error executing start work action

    Error: Request failed with status code 405

    Can also confirm that I cannot switch my status in Jira from the extension either (but works fine from the normal web interface). It does not show an error code when I try to switch status, just doesn’t update.

  3. Ilya Valmianski reporter

    With the new update it doesn’t work at all anymore. Doesn’t even start new branch/etc even if “transition issue” is turned off.

  4. Log in to comment