Disable VSCode link in Jira Issues

[rsbeckerca]

We do not use VSCode in our organization and cannot for this project. Jira issues are showing a start work in VSCode button which is confusing out team. We are an ECLIPSE/IntelliJ shop and do not want real estate on our issues, and team member confusion from this integration that we do not want.

Is there any way to hide it and/or replace it with a link to ECLIPSE?

Thanks,

Randall

[Elena Vladimirova]

Same here. Paying tens of thousands of dollars so Atlassian can essentially run ads on our real estate - classic!

[Mathijs de Kruyf]

Experiencing the same issue. Issue seems related to https://community.atlassian.com/t5/Jira-Software-questions/How-to-Disable-or-Hide-quot-Start-work-in-VS-Code-quot/qaq-p/1530814

[Remko Brenters]

I created a ticket for this: https://jira.atlassian.com/browse/JRACLOUD-75552

[Tim O_Brien]

As a company in a regulated industry, we have specific vendor & product procurement processes. You advertising inside a paid product is an invite for someone in my organization to sidestep these procurement processes, creating another "shadow IT platform" creating an audit finding and an incident. 

Remove this "invite" ASAP. 

[rsbeckerca]

This is a crucial issue that Atlassian must really consider. This point alone would be enough justification to cause a major issue with some of my larger customers.

[Ben Berry]

Agreed with everyone on here.  I'm spending more than 6 figures on our instance.  This is absolutely unacceptable to essentially paste an advertisement.  Now I'm answering questions on what this is and disappointing people.

[Angélica Luz]

Hello everyone,

Jumping on this thread to share with you an update from our developers regarding VSCode. 

It was posted on the thread Mathijs mentioned and also on the feature Remko shared. 

Hi everyone, I'm a developer at Atlassian.

We are working on an update that will change the initial glance to be more generic and will allow opting out of seeing the glance at all.

Thanks for your patience!

In case you have any other questions, please feel free to post it on the feature request. Also, make sure to watch it, so you will be notified when our developers post updates.

Regards,
Angélica

[Lex Talionis]

Hope your triage goes well.  Please ask the product team to back away from this kind of garbage and figure out why they didn't know this would create a huge uproar.

[Adrian Rutter]

Same here, we can control extensions, why does Atlassian think they can ignore our wishes and enable something we cannot disable.

[rsbeckerca]

We are still seeing VSCode reference all over the place. This is still causing issues. The Human Resources cost is escalating.

[Angélica Luz]

Hello @rsbeckerca,

Checking the details of the feature request ticket and also the internal escalation, the VSCode escalation was supposed to be removed from all sites since November 2020. Since you are still facing this issue, I created a ticket with our support team, so they can access your site and check why your site still has this extension.

You should have received an email with the link to the ticket and soon someone will contact you:

• https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-646036

[rsbeckerca]

There are new approved tickets to add VSCode back in. I am getting pretty frustrated with Atlassian's triage and product management. Maybe communication with your users would be a good plan?

[rsbeckerca]

Despite comments about removing VSCode, the links are still there. This is really frustrating. Atlassian is making strange decisions these days about product capabilities. The three dots in BitBucket pull requests now contain the View in VSCode option.

[Deleted user]

Same here, we did not ask for this.

[Nickson]

Same here