Jira Extension in VS Code Unassigns Ticket When Starting Work

[samarthpatel1289]

Describe the bug
When using the "Start Work" feature in the Jira Extension for Visual Studio Code, the ticket becomes unassigned from the user instead of keeping them as the assignee.

To Reproduce
Steps to reproduce the behavior:

• Open Visual Studio Code.
• Navigate to the Jira Extension panel.
• Select a Jira ticket assigned to you.
• Click on "Start Work."
• Observe that the ticket is unassigned from you.

Expected behavior
The ticket should remain assigned to the user after clicking "Start Work" in the Jira Extension.

Environment and Version

• Atlassian Plugin Version: 3.0.10
• Visual Studio Code Version: 1.97.2 (Universal)
• • Commit: e54c774e0add60467559eb0d1e229c6452cf8447
• • Date: 2025-02-12T23:20:35.343Z
• • Electron: 32.2.7
• • ElectronBuildId: 10982180
• • Chromium: 128.0.6613.186
• • Node.js: 20.18.1
• • V8: 12.8.374.38-electron.0
• • OS: macOS (Darwin x64 23.6.0)
• Is this a local or cloud environment? Cloud

[aledt]

To add to this, I think this has changed in a recent version - our workflow used to be use the plugin to change status and assign to the developer when using "Start work". The option to assign no longer seems to be available/working. Currently trying to pin down when this changed.