• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      I understand VS Code is fun to work with and you guys want to share your enthusiasm with the community. However it would be nice if you asked me first:

      'Hey paying customer, would you like us to add a reference to VS Code in your issue-screen?'.

       

      What are we talking about? This thing:

            [API-343] Remove VS Code integration (or make it opt-in/out)

            rod added a comment -

            Happy about the quick fix!

            rod added a comment - Happy about the quick fix!

            rsbeckerca added a comment -

            Thank you for getting this done so quickly.

            rsbeckerca added a comment - 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. 

            George DeCherney added a comment - 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?

            Jens Koester added a comment - 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.

            Remko Brenters added a comment -  Thank you m@. Life is good again.

            G$mith added a comment -

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

            G$mith added a comment - @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.

            m@ (Inactive) added a comment - 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.

            Trent Murray added a comment - - edited

            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.

            Trent Murray added a comment - - edited 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.

            G$mith added a comment -

            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.

            G$mith added a comment - 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.

            rsbeckerca added a comment - 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.

            p0cket0m added a comment -

            Even better!

            When do these marketing nerds finally recognize that forceful advertising never will work for the companies they work for. It harms.

            p0cket0m added a comment - Even better! When do these marketing nerds finally recognize that forceful advertising never will work for the companies they work for. It harms.

            Opt in, not OPT OUT 

             

            Tim O'Brien added a comment - Opt in, not OPT OUT   

            p0cket0m added a comment - https://community.atlassian.com/t5/Jira-Software-questions/Annoying-Advertising-quot-VS-Code-quot-field-showing-up-in-all/qaq-p/1531241  

            Thank you for all your feedback. We are reviewing this feedback and are making some adjustments to the implementation while allowing customers to disable the button if they do not want it there. We should have the release of the changes out in a couple of days.

            Shane Wade added a comment - Thank you for all your feedback. We are reviewing this feedback and are making some adjustments to the implementation while allowing customers to disable the button if they do not want it there. We should have the release of the changes out in a couple of days.

            Do I really need VS Code integration in Jira Service Management (old Service Desk) projects? No. Please remove it or give us the solution how to remove from view.

            Mateusz Daleki [Codedoers] added a comment - Do I really need VS Code integration in Jira Service Management (old Service Desk) projects? No. Please remove it or give us the solution how to remove from view.

            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. 

             

            Tim O'Brien added a comment - 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.   

            Please, remove the vs code adware. VS Code is as far I know for script kiddies or not so heavy projects, whereas we use Jira for heavy things and use heavy duty tools for it. 

             

            You have introduce new issue view with stripped features and now embrace features a small group only need.

            Piotr Bojko added a comment - Please, remove the vs code adware. VS Code is as far I know for script kiddies or not so heavy projects, whereas we use Jira for heavy things and use heavy duty tools for it.    You have introduce new issue view with stripped features and now embrace features a small group only need.

            Why Atlassian - why??? This seems to be just in line with the old custom domain ticket - https://jira.atlassian.com/browse/CLOUD-6999

            Since even –4658 Upvotes are ignored I have little hope to get rid of this any time soon 

            Michael Schramm added a comment - Why Atlassian - why??? This seems to be just in line with the old custom domain ticket - https://jira.atlassian.com/browse/CLOUD-6999 Since even –4658 Upvotes are ignored I have little hope to get rid of this any time soon 

            please remove this advertisement, it caused confusion across our organization and almost got someone fired

            Jad Meouchy added a comment - please remove this advertisement, it caused confusion across our organization and almost got someone fired

            Dear folks, please take it out. No value for us.

            Harry Rombach added a comment - Dear folks, please take it out. No value for us.

            Do we know this was a decision and not a simple mistake?

            George DeCherney added a comment - Do we know this was a decision and not a simple mistake?

            chris.hamilton added a comment - - edited

            Dear Atlassian,

            1. Find your product manager who crowbarred this mandatory and unwanted adware feature this into the software, impacting all users. 
              109 people have already voted within just eight hours to have it removed.
            2. Arrange a meeting with that product manager warn that his/her decision was grossly inappropriate.
            3. Kindly remove this adware feature ASAP

            chris.hamilton added a comment - - edited Dear Atlassian, Find your product manager who crowbarred this mandatory and unwanted adware feature this into the software, impacting all users.  109 people have already voted within just eight hours to have it removed. Arrange a meeting with that product manager warn that his/her decision was grossly inappropriate. Kindly remove this  adware feature ASAP

            An ill thought out addition inconveniencing many users and satisfying few. 

            Adam Marshall added a comment - An ill thought out addition inconveniencing many users and satisfying few. 

            rod added a comment -

            Wow.

            Jira items are places where working must be efficient, not a bulletin board where we should learn about new integrations... A blog or a mailing list are better fit for this kind of information.

            rod added a comment - Wow. Jira items are places where working must be efficient, not a bulletin board where we should learn about new integrations... A blog or a mailing list are better fit for this kind of information.

            oooooof, someone deployed a bad idea and now the internet is on fire about it. 🍿

             

            To be clear, 0 of my users want or need this as the project we manage isn't code, much less use VS.

            Lex Talionis added a comment - oooooof, someone deployed a bad idea and now the internet is on fire about it. 🍿   To be clear, 0 of my users want or need this as the project we manage isn't code, much less use VS.

            Tom Holden added a comment - - edited

            I agree with many above. This is taking valuable screen space for something that about 2 of my developers use. Please make any of this opt-in only! By the way, this seems to have broken the display of my Development field when content is not empty!

            Tom Holden added a comment - - edited I agree with many above. This is taking valuable screen space for something that about 2 of my developers use. Please make any of this opt-in only! By the way, this seems to have broken the display of my Development field when content is not empty!

            "Glance"? Nice wording for advertisements you're pushing into paying customers' faces. Rather feels like a pile of dog poop in front of my office door I'm accidently stepping into...

            Tobias Dörnbach added a comment - "Glance"? Nice wording for advertisements you're pushing into paying customers' faces. Rather feels like a pile of dog poop in front of my office door I'm accidently stepping into...

            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.

            brainicorn (Inactive) added a comment - 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.

            @simas aleksiejunas : That suggestion isnt exactly correct. the selector appears not to be unique. for example in our setup we also link Zendesk tickets and here is the result:  so the filter would block both out.

            George DeCherney added a comment - @simas aleksiejunas : That suggestion isnt exactly correct. the selector appears not to be unique. for example in our setup we also link Zendesk tickets and here is the result:  so the filter would block both out.

            Ted Pricer added a comment -

            I don't use VS Code and don't want to see a link to it.  Isn't this what plugins are for?

            Ted Pricer added a comment - I don't use VS Code and don't want to see a link to it.  Isn't this what plugins are for?

            joehardin added a comment -

            Agree with this request. Adding this in by default is nonsense and is noise for the majority of users

            joehardin added a comment - Agree with this request. Adding this in by default is nonsense and is noise for the majority of users

            We can't rely on the software that can get random not removeable banner any time. It's a very bad practice 

            Dmitry Astapkovich _Colined_ added a comment - We can't rely on the software that can get random not removeable banner any time. It's a very bad practice 

            Remove that crap

            daniel.huser@sap.com added a comment - Remove that crap

            For those as annoyed as I am, here's a handy uBlock Origin filter, to remove the div with the ad:

            atlassian.net##[data-test-id="issue.views.issue-base.context.ecosystem-glance-panel"]
            

            Simas Aleksiejunas added a comment - For those as annoyed as I am, here's a handy uBlock Origin filter, to remove the div with the ad: atlassian.net##[data-test-id= "issue.views.issue-base.context.ecosystem-glance-panel" ]

            Dan Crough added a comment -

            Where is a response from Atlassian? Need to know how soon this will be removed.

            Dan Crough added a comment - Where is a response from Atlassian? Need to know how soon this will be removed.

            Microsoft Team Foundation Server suddenly looks more interesting to me now that "features" like this one are implemented.

            If you want to keep your customers, better stop the forced advertisements right away!

            Olaf Egbers added a comment - Microsoft Team Foundation Server suddenly looks more interesting to me now that "features" like this one are implemented. If you want to keep your customers, better stop the forced advertisements right away!

            Yes, please remove – it is confusing our dev team as we do not use VS Code

            Ryan Johnson added a comment - Yes, please remove – it is confusing our dev team as we do not use VS Code

            Coming Soon, Ad Removal from cloud products $99.99

            chrisharshman added a comment - Coming Soon, Ad Removal from cloud products $99.99

            Yury V. Zaytsev added a comment - - edited

            Doesn't matter - I'm not paying for being served irrelevant ads on an A/B test basis.

            P.S. It only makes it even worse - it means that someone must have thought that what they are doing is not right and if they turn it on for everyone simultaneously there will be a backlash. So yeah, let's try to see if a small group of people think whether the unasked for ads in a paid-for product are acceptable and gauge the dissatisfaction first before it spins out of control. The ethical behaviour would have been: "it doesn't feel right - just don't do it".

            Yury V. Zaytsev added a comment - - edited Doesn't matter - I'm not paying for being served irrelevant ads on an A/B test basis. P.S. It only makes it even worse - it means that someone must have thought that what they are doing is not right and if they turn it on for everyone simultaneously there will be a backlash. So yeah, let's try to see if a small group of people think whether the unasked for ads in a paid-for product are acceptable and gauge the dissatisfaction first before it spins out of control. The ethical behaviour would have been: "it doesn't feel right - just don't do it".

            George DeCherney added a comment - - edited

            Looks like it might be an A-B test as I found this in the HTML of the ticket ... `data-test-id="issue.views.issue-base.context.ecosystem-glance-panel"` 

            George DeCherney added a comment - - edited Looks like it might be an A-B test as I found this in the HTML of the ticket ... `data-test-id="issue.views.issue-base.context.ecosystem-glance-panel"` 

            @Scott I was updating add ons at the same time and just thought I broke something. Jira Product team needs to go in the corner and feel ashamed for a good one hour. 

            Elena Vladimirova added a comment - @Scott I was updating add ons at the same time and just thought I broke something. Jira Product team needs to go in the corner and feel ashamed for a good one hour. 

            We are not using VSCode at all. So, why should I see this option? 

            Manfred Koch added a comment - We are not using VSCode at all. So, why should I see this option? 

            Adding one more comment to the pile:

            I think we've probably all gone through the stages of:

            • What's that?
            • Have I added this to one of my screens by accident?
            • All my screens?!
            • Is it a custom field?
            • No. So it is a built in field?
            • Is it a plug in?
              (* And maybe clicking on it, and finding the link brings up something in Microsoft's store - which is even weirder)

            Then finally Googling to find this.

            This may be some error on Atlassian's side, but if it is a marketing attempt, it's having the exact opposite effect.

            Scott Fannen added a comment - Adding one more comment to the pile: I think we've probably all gone through the stages of: What's that? Have I added this to one of my screens by accident? All my screens?! Is it a custom field? No. So it is a built in field? Is it a plug in? (* And maybe clicking on it, and finding the link brings up something in Microsoft's store - which is even weirder) Then finally Googling to find this. This may be some error on Atlassian's side, but if it is a marketing attempt, it's having the exact opposite effect.

            I was examining the audit logs, and going through all the settings screens to see if there was a plugin added.

            Maurice Samulski added a comment - I was examining the audit logs, and going through all the settings screens to see if there was a plugin added.

            Thank you for opening this issue. My suggestion here is to provide a more generic solution. If you are going to provide a link to VSCode, you should provide a link capability to other IDEs, including XCode, ECLIPSE, and IntelliJ - this could be something configurable by the project administrator. Presumably some teams might use multiple IDEs. We are an ECLIPSE/IntelliJ shop, with VSCode used only in one isolated project. The use of ECLIPSE is not "mandated". It is required based on the available host platform tools (compiler pre-processors for SQL).

            rsbeckerca added a comment - Thank you for opening this issue. My suggestion here is to provide a more generic solution. If you are going to provide a link to VSCode, you should provide a link capability to other IDEs, including XCode, ECLIPSE, and IntelliJ - this could be something configurable by the project administrator. Presumably some teams might use multiple IDEs. We are an ECLIPSE/IntelliJ shop, with VSCode used only in one isolated project. The use of ECLIPSE is not "mandated". It is required based on the available host platform tools (compiler pre-processors for SQL).

            Please make it opt-in option. It's harmful for my UX. I feel my cognitive resource is wasted.

            Ryuichi Kokubo added a comment - Please make it opt-in option. It's harmful for my UX. I feel my cognitive resource is wasted.

            My first though was that our Jira Instance was hacked

            Yury V. Zaytsev added a comment - My first though was that our Jira Instance was hacked

            Dear Atlassian,

            We're paying pretty good money for your solution, so we expect it to be ad free.

            Thanks,
            Elena

            Elena Vladimirova added a comment - Dear Atlassian, We're paying pretty good money for your solution, so we expect it to be ad free. Thanks, Elena

            I'd also appreciate this being opt-in. VS Code is a good editor but I don't need it to pollute my ticket overview.

            Deleted Account (Inactive) added a comment - I'd also appreciate this being opt-in. VS Code is a good editor but I don't need it to pollute my ticket overview.

            Orchestrade Inc added a comment - - edited

            Please remove unexpected "VS Code" field from issue view.

            Orchestrade Inc added a comment - - edited Please remove unexpected "VS Code" field from issue view.

            Please make it possible for us to remove the 'VS Cloud' field from all our Jira tickets. It's causing confusion!

            Simon Mann added a comment - Please make it possible for us to remove the 'VS Cloud' field from all our Jira tickets. It's causing confusion!

            Yes, I would also like to remove this link since we do not need it.

            mikhail.banduryan added a comment - Yes, I would also like to remove this link since we do not need it.

              mjensen m@ (Inactive)
              03a8f090607f Remko Brenters
              Votes:
              150 Vote for this issue
              Watchers:
              76 Start watching this issue

                Created:
                Updated:
                Resolved: