Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-42068

Allow disabling "on the fly" creation of new components and/or versions

    • 14
    • 17
    • Hide
      Atlassian Update – 8th February 2018

      Hi Everyone,

      Thanks for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

      This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 8th February 2018 Hi Everyone, Thanks for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      The on the fly creation makes it too easy to create unwanted items. This is especially true for components, which are typically created only rarely, so the extra steps are not a problem. An option to disable this feature would be very welcome.

      The same sentiment is expressed in https://answers.atlassian.com/questions/317066/prevent-on-the-fly-component-creation

            [JRASERVER-42068] Allow disabling "on the fly" creation of new components and/or versions

            The ticket is only nine years old. After such a short period of time, you can't really expect a substantive response from Atlassian. The fact that it's just not being implemented is causing a lot of anger and work for us. I've been following this ticket since 2017, and I don't expect it to be implemented before I retire. 

            Helmut Schreiber added a comment - The ticket is only nine years old. After such a short period of time, you can't really expect a substantive response from Atlassian. The fact that it's just not being implemented is causing a lot of anger and work for us. I've been following this ticket since 2017, and I don't expect it to be implemented before I retire. 

            Any progress?

            I would also like to authorize "on the fly" creation of new components, labels and/or versions.

            Michiel van Everdingen added a comment - Any progress? I would also like to authorize "on the fly" creation of new components, labels and/or versions.

            that's right and we are willing to switch, but what good solution is there for Jira /Bitbucket/Confluence

            Michael Kornatzki added a comment - that's right and we are willing to switch, but what good solution is there for Jira /Bitbucket/Confluence

            They're too busy chasing acquisitions to deliver customer-requested features.    Why companies still favor this relic of a software suite is beyond me.

            Richard Zeliff added a comment - They're too busy chasing acquisitions to deliver customer-requested features.    Why companies still favor this relic of a software suite is beyond me.

            It's incredible.
            For 6 years, this requirement exists for a not cheap software but no one wants to solve it

            Michael Kornatzki added a comment - It's incredible. For 6 years, this requirement exists for a not cheap software but no one wants to solve it

            Dear Atlassian please add this feature!

            Vasiliy Grizel added a comment - Dear Atlassian please add this feature!

            Would be useful in Servicedesk. We have less well-informed team members who are creating issues in "the back-end" of Servicedesk, then creating Components which don't map to our agent queues, are mis-spelt, duplicate, and generally unhygenic.

            Simon Pearce added a comment - Would be useful in Servicedesk. We have less well-informed team members who are creating issues in "the back-end" of Servicedesk, then creating Components which don't map to our agent queues, are mis-spelt, duplicate, and generally unhygenic.

            Vijay Sv added a comment -

            Agreed, Dear Atlassian please add this feature.

            Vijay Sv added a comment - Agreed, Dear Atlassian please add this feature.

            This needs to be fixed please. It is very annoying and causing reporting issues. 

            Jason Campo added a comment - This needs to be fixed please. It is very annoying and causing reporting issues. 

            Dear Atlassian, please listen to your customers and make this "feature" optional.

            Rainer Mueck added a comment - Dear Atlassian, please listen to your customers and make this "feature" optional.

              Unassigned Unassigned
              3330761b77e4 Daniel Bonniot
              Votes:
              377 Vote for this issue
              Watchers:
              178 Start watching this issue

                Created:
                Updated: