Happy about the quick fix!

Thank you for getting this done so quickly.

Thanks m@ for rolling out the update. 

Not sure if this is the right medium for this type of feedback but when you all do decide to roll it out it would be great if it were a per user setting and not a per project setting. For example, on my team we have some people that prefer to use VS Code and would enjoy such a feature and some people that dont use VS Code that would find the additional item on the view to be in the way. 

Why did you think our legal support need this in jira service desk?
Why did you think our finance team need this in jira core?
Why did you think serious developer need this in jira software?

 Thank you m@. Life is good again.

@m@, Thank you for correcting this for all of us so quickly!

Hi everyone,

Thank you for bringing this issue to our attention.

This change was introduced as part of an experiment in relation to our VS Code integration and was mistakenly rolled out to all users.

We apologise for any inconvenience or confusion that we've caused. The change has been rolled back and the VS Code field will no longer appear on your issue view.

This is a serious achievement for Atlassian. You've managed for the first time, and with amazing effectiveness to piss off the ENTIRE cross section of your user base. From developer teams, to non-developer teams. 

What a special day.

Now, do us all a favour - and quietly, and swiftly remove this crap from our Jira screens.

We're in the same situation as @rsbeckerca: we are on-boarding several new employees and are also transitioning to some different tools.  Having a spammy advertisement for a non-sanctioned tool could turn into a support nightmare.  (I'm surprised no one has called me yet asking to use it.)  Let alone the fact that it's just clutter in the way of our work.

Please remove it as quickly as you can.  Since it's been a "feature" for awhile, there is no need to clutter and confuse our users.  As others have mentioned, highlighting the integration in an administrative E-mail would have been sufficient.

I agree with Tim O'Brien. This must be an Opt-In feature, not Opt-Out. And it should be policy for future ad-based features. We don't want rogue code showing up in our organization. You are operating inside our protected zone. Accidental (or deliberate) unauthorized downloads and even ads that encourage unauthorized downloads are serious issues from a security, compliance, and HR standpoint. We are in an onbording phase with new staff getting used to Jira and the last thing we want is to have spend time and salary to monitor every single project/product for potential ads from a trusted supplier that our Jira newbies might take as sanctioned by our company. This is simply not acceptable. We have been a BitBucket customer for years, but just converted to Jira and I am having cautionary misgivings.