• 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:

          Form Name

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

            Richard Hornsby added a comment - - edited

            Hi JIRA. Why is this back? Reading this thread, it seems like we (us users and you JIRA) agreed that forcing this VSCode onto us was better as opt-in. I don't know exactly when it happened, but there's an "Open in VSCode" button again in SaaS JIRA.

            Please remove it.

             

            Edit: sigh. Images are disabled after creating the comment? The "Open with VS Code" appears on the right side immediately below the "Reporter" field and above the Github integration options (Development)

            Richard Hornsby added a comment - - edited Hi JIRA. Why is this back? Reading this thread, it seems like we (us users and you JIRA) agreed that forcing this VSCode onto us was better as opt-in. I don't know exactly when it happened, but there's an "Open in VSCode" button again in SaaS JIRA. Please remove it.   Edit: sigh. Images are disabled after creating the comment? The "Open with VS Code" appears on the right side immediately below the "Reporter" field and above the Github integration options (Development)

            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.

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

                Created:
                Updated:
                Resolved: