Can't enable Jira/bitbucket integration via a per workspace setting.
When Jira and Bitbucket are disabled for the User and enabled in the workspace, the configuration bar at the bottom doesn’t show up. The Atlassian A
doesn't either in the left hand side menu.
Wanted situation: To be able to enable it per workspace. Instead of enabled globally and disabled for every workspace that doesn’t use Jira/bitbucket.
Comments (11)
-
reporter -
reporter - edited description
- changed title to Can't enable Jira/bitbucket integration via a per workspace setting.
-
@Roland van Laar
, to make sure I understand the issue, are you saying if you activate the extension for the open workspace via the Extensions sidebar it never loads? Or does it load but then fails at some future point.Edited: Disregard, I understand the issue now.
-
- changed status to open
-
Account Deactivated - changed status to resolved
Version 2.1.5 fixes this issue. Please update and try it out.
-
reporter Thank you, I had the same problem with other extensions: https://code.visualstudio.com/docs/editor/extension-gallery#_enable-an-extension
-
reporter What happens now is that the Atlassian Logo doesn’t show up in the side bar.
I tried uninstalling and installing again.
I am however on the VSCode august release due to a python bug.
-
Account Deactivated - changed status to open
@Roland van Laar I'll keep this issue open in that case and we'll continue investigating.
-
@Roland van Laar , assuming you’ve disabled the extension at the User level can you try toggling the setting at Workspace level (even if it appears to already be enabled)?if you’re disabling the extension at the User level and then switching
-
reporter Toggling it on and off at the workspace level made it work.
And consider me to be very positively impressed by Jira
for one of the first times.
The ‘JIRA ISSUES’ panel in the extensions shows me the epics and the issues in that epic as a tree. That’s one thing that makes it much more clear to me.
I like it.
-
- changed status to resolved
- Log in to comment
This seems related to this closed issue: https://bitbucket.org/atlassianlabs/atlascode/issues/54/make-site-project-configurable-per-vs-code