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.

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.

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!

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.

Agreed, Dear Atlassian please add this feature.

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.

on-the-fly creation of component and version is not reasonable. Because the components and versions will be controlled by product manager (some role like that), but if someone has resolve permission then he could add the new one. You will see lots of the versions and components are unuseful and some issues were linked with them. This is a stupid design of permission schema. And Atlassian won't improve it.

The possible solution will put a trigger based on issue event and prevent it happen. But by now I didn't try it out. However, if someone has update solution, please let me know. 

Are we reviewing the need of this feature? This holds a lot of value for places where there are multiple teams working in parallel.

This ticket (created in 2015) was marked "Not being considered" with a remark stating it to be reviewed again in an year. Are we planning to fix the same as would have a lot of value to it and would help in limiting a lot of unnecessary/ duplicate data being created, leading to a better and clean reporting and tracking, the core objective of tools like this.

Just some statistics : we have > 100 projects, > 1000 versions overall. Last year alone, we had to delete exactly 258 versions that were created without intention by users making mistakes... Each time trying to fiddle out to what version the issues assigned to such erroneous version should go.

Not to speak from issues (bugs) we missed because they were attached to such phantom-version...

Can someone from Atlassian raise one (1), just one, use case were this feature adds value and raises performance of a team ?

How presumptuous from Jira Product team to dictate what their paying users should or should not get in return of their money. This is an absolutely ridiculous feature, considered by many as a bug and all Atlassian has to say is "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 issue can mess reports, board lanes, filters, you name it...

• If you were unable to implement all of the excellent suggestions people did, try harder... Or at least implement JUST ONE!
• You don't plan to work on this for the foreseeable future? I'm gobsmacked you plan at all!

Atlassian = 

Will create a new component when a project admin has a typo in the component they are trying to search for. Now have a long component list filled with duplicate components. Please change the implementation so that its easier to select similar components and requires further confirmation to create a new component on the fly.

IMHO the creation of new component is implemented wrong- or at least it is just too easy.

There should be an extra step to create new, e.g. item in drop-down list "Add new..." then maybe even a popup opens to ask details of new component/version. Or

Also noticed that when creating new issue, and typoed new component but managed to remove it from the list before clicking Create, the Issue created -notification still says that a new component has been created even it has not been created. (and again i go to project settings -> components just to see it is not there)

For now, i'm considering to hack the vm files to disable this.

+1
Still waiting any solution for manage this feature-bug

This is a bug for us and not a feature
We work and sort according to predefined components.
Please disable this bug / feature. Thanks.

Having components created on the fly is a nuisance, especially when the whole company is using the product.  We assign tickets based on component and having on the fly component creation increases error rates in assignment since it then has to go to someone with the sole purpose of editing the component and re-assigning - and then we have to go in and delete the unwanted component that was created on the fly.  Please, please give us the option to disable on the fly component creation.

Would be nice if Jira could start thinking from an Agile perspective.  I am sure many Agile teams want to restrict defining components and versions to product owners or Scrum masters.  

Even project Administators could misspell the version. We would need disabling "on the fly" creation. Thanks.

Please reconsider this decision.  It is so easy to accidentally create new versions that you don't want.

Please reconsider this change.  It is so easy to accidentally create new versions that you don't want.

A solution that worked for us was to change that field to a List Selector renderer. That has solved most of our issues with on-the-fly component creation.

You guys apparently forgot that you have users. If one user point to a "feature" calling it a "bug", the well... but if 250+ calls it a bug, then maybe they are right, not you. This "feature" sucks. It sucks so much that your post, Jakub, is almost clear indicator you do not use Jira on daily basis. Otherwise you'd step on that "feature" already enough times to upvote the request of fixing this "feature".

I am just wondering what else if not this ... i am just wondering what important new features, improvements or bug fixes will be part of the release notes this year as obviously this is not so important based on the Atlassian meaning.

So you've implemented a "feature" that nobody asked for, and that causes more harm than good... then after receiving nearly 250 votes to get rid of it, you still respond with "tough, live with it" ?  In the time it took you to write that response you could have reverted the "feature".  This isn't rocket science.

This is disappointing. I don't consider this a feature, but a bug. At minimum the ability to turn off  the function should be considered, or removing the "feature" altogether.

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

+1

+1

+1

+1000

+1

+10

+1

+1

+1, creating components is pretty rare and we try to define the buckets in a helpful way along with corresponding filters/component watchers/etc. When a user creates a new component it may get lost right away.

I generally love JIRA, but this has to be one of the worst 'features' implemented in one of the worst ways. Took the time to make an account just to upvote this issue. Where is the relief Atlassian? This issue seems to bother a lot of people.

Personally I want only admins to create a versions / components. It take time to keep cleaning this up.

Leon's comment (https://jira.atlassian.com/browse/JRA-42068?focusedCommentId=777034&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-777034) about changes to a .vm file for versions should also work for stopping on-the-fly creation of components. Make the same change to atlassian-jira/WEB-INF/classes/templates/jira/issue/field/components-edit.vm

This is about the simplest source level change I can think of. Attempting to set the boolean using javascript in the banner or a field description is more complex since you have to handle regular pages and pop-up windows for this.

Automatically creating versions makes little sense for us and seems like a bug.  The previous functionality restricted input in the field to valid versions, providing an error check to the user.  Restricting to project admin doesn't help because the project admin is generally the one who assigns Fix Versions and uses the field the most!

We create a new version about every 3-4 months but type into the Fix Version field many times a day.  Often, someone misspells the version name or types the wrong text into it thinking it is a different field.  This results in a bunch of work on someone to pro-actively discover and delete the invalid version(s) that JIRA auto-created.

If there was some better visual feedback that you are creating a new version, this functionality would be improved.  For example, when typing quickly you don't see the "(New version" text, and instead all you see is the version box (or lozenge?) with the x.  If this version box showed up as a different color or with an icon in it indicating you are creating a new version I think the user would notice it before pressing ENTER/Apply.

I created a question here before I found this ticket: https://answers.atlassian.com/questions/56462839/how-to-prevent-jira-fix-version-field-from-automatically-creating-new-versions

This is something that is needed very badly. There should be an option to only allow component creation through the admin interface. This leaves you with two simple options, anyone can create components like today or a more restrictive setup where components are provided and only added when needed by project admins. This is a huge mess for us to keep clean as it is easy for people to just add components they think need to be there.

+1 Extremely inconvenient as now somebody has to go and cleanup components and merge versions every couple of days, or otherwise it quickly becomes the mess with all those "v.1.2.3, ver.1.2.3, Version 1.2.3, 1.2.3, v123" variations of the same thing.

I do not care granularity personally. I just need the users to not create new components/versions on-the-fly, so I am fine with just "only admins" implementation - still better than the mess users create (which costs time to clean up)

We are having the same issue. This makes reporting a challenge and it is just messy.

We are having this issue pop up as well and would like the ability to restrict it by role or something similar.

We needed this 'On the fly' version and component creation "feature" like a hole in the back. Please stop the pain. Thank you.

+1 please

+1, even though I do believe that only (project) administrators are allowed to do this.

I also have the same requirement, not to allow on the fly component creation.
Not sure why Atlassian is not give priority to this enhancement request.

I suspect you cannot disable it by just disabling an add-on module. I agree that this feature can cause serious problems in projects with lots of project administrators.

Atlassian, please would you add some feedback here

I don't know why this isn't getting any action from Atlassian. This is a major pain point for us and all of the other organizations that have commented here.

+1, Me too.

+1, agree with David Peacock

This is creating a lot of reporting problems because users are inadvertently creating new components. 100+ so far in a project.

The moment components are synced with another product, in our case SpiraTeam for testing, a situation in which the items must be carefully set up, this on-the-fly creation of components is very problematic.

I agree with this.

+1

This is a problem to us, where component are sometime similar but not identical between projects.

At the very least, the interface should prompt the user before creating a new component / version inline.

@dschorow if your Jira is hosted in Atlassian cloud, you won't be able to do so.

@Leon - is this a solution one can use with the hosted Jira system?

you can change the version velocity template file at <<jira_installation_path>>\atlassian-jira\WEB-INF\classes\templates\jira\issue\field\versions-edit.vm
change data-create-permission="$!

" to data-create-permission="false"

Doing this disallows creating new version in issue creation page

+1

+1

Completely agree with David Peacock (and thus David Schorow)!

Yes - what David Peacock mentions is the problem. Lots of people have admin authority since that is needed for sprint work.

The "Project Admin" role is needed to do this on the fly creation - but this role is also needed to create sprints in Jira agile. All our scrum masters need this role and it is not reasonable to educate your way out of this. Say you've been using a version for a while and decide to rename it. People will continue entering the wrong thing.

It must be a configurable property of the field.

only a user in project role "Project Admin" can create new versions and components on the fly. Setting-up the project roles properly can significantly limit the problem since Project Amins are mostly reasonable people.

I'm not sure, but I think you have to be a Project Admin to set up an Agile board. We need to let a wide range of people do that.

I agree. Limited to Project Administrators is satisfactory.

Yup, it works for me on version 6.4.4. User without Project Admin cannot add new component on the fly.

We are using Jira on demand and we found a workaround for the problem - only a user in project role "Project Admin" can create new versions and components on the fly. Setting-up the project roles properly can significantly limit the problem since Project Amins are mostly reasonable people.

I have a plenty work to do to delete the "new" components. Please give me the possibility to restrict that.

Please allow the option to restrict component creation on the fly within a ticket. It is very easy to create new components by mistake, even by the admins! In my project we have a set number of components, I don't want to accidentally type 'pecification chart' when I mean 'specification chart' and have the new typo'd component now always prompt as an option. It happens all the time.

When have many filters based on components and It's a huge fear of mine that a ticket gets assigned a wrong component and will not show up in the correct work queues.

This is a very strange thing to allow users to do. We use JIRA as a service desk and have a set of components to direct tickets to component owners. The change allowing ad-hoc components has mostly broken this. Now tickets end up assigned to the project owner very often, they don't get looked at in a timely manner, and users are unhappy.

Please fix this.

This option is important to have a better management of component list.

We have the same issue: I tight set of components that dispatch requests to the according department/person. Adding new components on the fly creates quite a mess and weakens our system.

Thanks in advance

This is also problematic for our Engineering team as they're noticing a proliferation of 'Versions' mistakenly being created. Please make this feature optional.

+1 on this Jira. This is a major pain point for our organization.