It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Prevent 'on the fly' component creation


1. Users need the project administrator permission to allow managing sprints
2. Since recent, users having the project administrator permission are allowed to create components 'on the fly'
3. Users submit data containing typing errors

Combining 1,2 and 3 results in a situation in which more and more faulty components are created and polluting the project. How can this be solved?


1. Users can manage sprints
2. Users are unable to create components 'on the fly'

5 answers

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="$!{createPermission}"  to data-create-permission="false"


Doing this disallows creating new version in issue creation page

We still have the problem in JOD, though...

Correct, you're not allowed to hack Cloud JIRA to implement downgrades like this one.

'hack'? 'downgrade'? At least your attitude is clear.

Although you will be the first to get it if Atlassian decouple "create sprint" from "component maintenance" (I doubt they'll ever do it with versions, as they're often needed as part of the sprint process)

Yes, it's a function most of my users had been yelling for for ages. It's clearly a downgrade to remove functionality that people like and want.

Agree with Nic on this. Restricting managing Components and Versions to jira admins is surely going backwards.

I created a feature request for this, vote for it if you agree:

1 vote

The permissions are not that granular. A project admin should be able to maintain components and sprints really, and the permissions to do that are one item (also includes the maintenance of versions and users)

If your users are entering the wrong words for components, you'd actually be best advised to get them to check their data properly! It's in their best interests to get it right anyway, get them to buy into it more.

Nic - we are experiencing the same problem.  We have a constant trickle of faulty versions and components being created.  This 'on the fly' technique makes it all to easy for people to accidentally create components and versions.  We need an option to disable this capability. 

I'm afraid there's nothing in JIRA to allow this to be turned off. Also, Atlassian are moving strongly towards this "quick entry" style of interface, and I'm afraid that the only real answer is "educate your users"

Good advice, but the problem is that in a large company you'll have a lot of people who need to be able to manage sprints, and these people might not be the same folks who are part of the team that manages components / versions. When you have an instance that gets on average 1500-2000 issues created a day, typos are bound to occur. Even with a 1% error rate, we're going to see this quickly cause issues. Now not all 1500 issues rae being created by someone with project admin access (bugs), but almost all our stories are entered by people with admin access (since they manage sprints). So just like Atlassian has the ability to disable inline editing, they will need to provide the ability to disable inline creating.

+1 on Jason's comment above. While we don't create 1500 issues a day, we create enough that monitoring and correcting errant versions and components is a regular job. We need a away to disable inline creation of components and versions.

+1 Components are typically used as categorical bins to arrange issues by; as such they aren't changing that frequently in a project, and certainly not something that needs to be added on issue creation. It's easy enough to create them on the project's board's Components view: type the name, tab, type lead, tab, type description, tab, select default assignee, tab, enter, rinse and repeat.


I had to create a custom field (closed list) to avoid this issue.

We have a lot of components, and a closed list is the best way for them to quickly see which component is the more adequate.

Creating components on the fly just lead to everyone creating their own component when frustrated to not find it in seconds.

+1 Component creation on the fly should be prohibited - it very error prone. Components aren't changed so much

Stop giving most people project admin rights if this is a problem for you.  Then educate your remaining project admins

to set data-create-permission="false" is sadly not a solution :(

Does anyone have another solution?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you