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; } } }

Limit ability to change component only to certain project roles

Rahul Aich [Nagra]

We would like to limit the ability to change the component only to certain project role members and not to everyone who has edit permissoins.

How is this possible?

Rahul

Accepted answers

Boris Georgiev [Appfire]

Look at this dicussion - I think it covers what you're asking

https://answers.atlassian.com/questions/208002/restrict-editing-of-select-issue-fields

All comments

Boris Georgiev [Appfire]

Look at this dicussion - I think it covers what you're asking

https://answers.atlassian.com/questions/208002/restrict-editing-of-select-issue-fields

Nic Brough -Adaptavist-

It's not. If you can edit an issue, you can edit it.

Jira doesn't do field level security. You could do it with the Quisapps field security plugin, or botch in some javascript (seriously, not advised), but Jira doesn't do it natively.

Or, you could move the edit into transitions and control them. Remove the components field from the create and edit screens in use, then put it on it's own screen. Then use that screen in transitions that go back to where they came from and are controlled by permissions matching your groups

Rahul Aich [Nagra]

thanks Boris..

Rahul Aich [Nagra]

Thanks Nic for your response. That helps.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration