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

Restrict changes to the priority field based on project role

Timo Scherer

Hi everyone,

is there a way to control who is able to alter the priority of a given issue? Ideally, I would be able to define which role is allowed to alter the priority state, thereby preventing everyone else from screwing up our priorization scheme.

Is there an option I have not found yet or would this function need to be implemented?

Thanks

Timo

Accepted answers

Fazila Ashraf

Hi @Timo Scherer

Welcome to community!

It is not possible to control who can perform edit operation on the field priority.

The general way of getting around this problem will be to not have 'Priority' field in the edit screen. But instead have a self loop transition (say 'Change priority') in the workflow that is restricted only to a given project role. In that transition screen, you can have the field priority.

Hope this helps!

All comments

Fazila Ashraf

Hi @Timo Scherer

Welcome to community!

It is not possible to control who can perform edit operation on the field priority.

Hope this helps!

Timo Scherer

That sounds promising. I'll look into it. Thanks a lot.

Lucas Knorr

Hi @Timo Scherer

there are two solutions for your requirement.

1. You can remove the priority from the screen that is linked to the edit action. This prevents the priority field from being changed for everyone. Then you implement an additional transition with a transition screen on which you place the priority field. You can use a condition to restrict the transition so that it is only available to certain users.

2. You license a plugin like Scriptrunner and utilize Behaviours. (https://docs.adaptavist.com/sr4jc/latest/features/behaviours/behaviours-supported-fields-and-products).

Trudy P Claspill

Adding to this....

Regarding option 1, Transition Screens are available only in Workflows used for Company Managed projects. If you are working with a Team Managed project, this option will not be available.

Trudy P Claspill

Note that the Transition Screen functionality will be available only if you are working with a Company Managed project. It will not be available if you are working with a Team Managed project.

Amulya Sankara

Hi @Trudy P Claspill

I have a team managed project and I'd like to set up controls on which users can change the priority of the issues. As you mentioned, I could not find the transition screen functionality.

Is there a way to set up such a restriction in team managed projects?

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-work-management

jira-work-management-cloud