Well, you need to be project administrator in order to create new components. So if you remove the Administer Projects permission you would not run into this issue.
https://confluence.atlassian.com/display/Cloud/Defining+a+Component
I would vote against this terrible 'enhancement' too. It's ridiculous that if you're an administrator, a typo insta-creates a component or version or whatever. Backing them out involves getting into the project administration, which is a UX asymmetry: it should be as easy to delete these phantoms as it is to create them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to repost as an answer what @Ben Ernst commented earlier (and many thanks to him for starting a ticket on it): https://jira.atlassian.com/browse/JRA-45176
Please go vote for this issue if you want this fixed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Robert Massaioli @Paul DeSousa @John Hawksley https://jira.atlassian.com/browse/JRA-45176
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you raise an issue? If so please post it here as I will vote for it, and need to do this myself. I would like to lock it even for administrators, and only allow adding of components by first unlocking the component add feature and then adding it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would raise an issue for this in http://jira.atlassian.com/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.