Make site & project configurable per VS Code folder/workspace
It would be great if the Jira site & project are saved per VS Code project, perhaps via a configuration file.
That way, opening a folder in VS Code would automatically authenticate you with the right site and project.
Comments (10)
-
-
reporter That's exactly it @markstickling
-
-
assigned issue to
It would be great if the Jira site & project are saved per VS Code project, perhaps via a configuration file.
That way, opening a folder in VS Code would automatically authenticate you with the right site and project.
-
assigned issue to
-
Just wanted to also say I would find this extremely useful. All my projects are organized by workspaces, would be great to be able to set project defaults.
-
Thanks for assigning the issue Jira Team. Hope it’s an easy change Nick 🤞.
I just wanted to add some clarity to my comment above:
I work at an agency so we have dozens of clients and active Jira projects. Each Jira project usually has one (occasionally a few) related repositories.
I usually set up a VSCode workspace for each repository I’m working on. So, it would be nice and convenient to open the VSCode workspace and have the correct Jira project selected each time.
-
@markstickling , are you able to access all the sites with the same Atlassian account or are there different accounts associate with each one?
-
In my agency situation - some Atlassian accounts are supplied to us by our clients and we work within those, and we have our own Atlassian account for our organization and use that as well. Would be great to be able to associate an Atlassian account with a workspace.
-
@Nick Rundquist my situation sounds much like @John Lomma 's above but maybe with a different split.
- 99.9% of the time I use one login to Jira on minttwist.atlassian.net that holds all of the Jira Projects that we project manage for our clients.
- Rarely for me [once in many years] a company we partner with has their own Jira setup that they want us to log into if they’re Project Managing and we’re supplying code. I currently don’t log into any other atlassian.net subdomains or self-hosted Jira local deployments but I have in the past.
I don’t know how common our situation is .
Hope this helps.
-
Account Deactivated - changed status to resolved
Version 1.4.0 of the extension updated the site and project setting to workspace-level instead of a global config. Please try it out. (Note that you need to update to VS Code 1.34 to use this version)
-
The caveat is that there continues to only be one Jira account logged in at a time so if you have projects that are only accessible from separate accounts you’ll still need to log out and log back in.
- Log in to comment
I often work on many projects a day with a VSCode Workspace set up for each. I would like to set the Jira project the sidebar shows for each workspace.
At the moment I seem to have to keep switching the project in the sidebar. I’m frequently looking at code for project A with issues in the sidebar for project B.
@Laurent Sorber does the above align with your experience?