nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Prevent 'on the fly' component creation

unknown

Context

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?

Requirement

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

Accepted answers

All comments

Nic Brough -Adaptavist-

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.

David Schorow

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.

Nic Brough -Adaptavist-

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"

unknown

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.

David Schorow

+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.

Daniel Bonniot

I created a feature request for this, vote for it if you agree: https://jira.atlassian.com/browse/JRA-42068

Leon Liu (ease

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

Kieran Sheehan

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

Nic Brough -Adaptavist-

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

Kieran Sheehan

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

Michael Kornatzki

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

Does anyone have another solution?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud