The gist is this: Employees who works with tickets can only edit and formalize tasks in the Support Review status, but I also need to prohibit editing of the "Assignee" and "Priority" fields in this status. I can prohibit editing of the "Assignee" field through the permissions scheme, but how can I prohibit editing of the priority field? This is the supervisor's job.
Hello @Varvara K_
There is no permission associated specifically with the Priority field. Users with the Edit Issue permission will generally have the ability to edit that field.
If you want to limit the ability to Edit the field you can consider this solution that applies only to Company Managed projects:
1. Remove the Priority field from the Edit Screen. It can remain on the View Screen.
2. Create a Transition screen and add the Priority field to it.
3. In the workflow create a new transition from Any Status to Itself and associate the new Transition screen to it.
4. Add Conditions to the Transition to limit who can execute that Transition, which therefore limits who can edit the Priority field.
No, this is not a good variant for our company. Maybe do any plugin exists, which may helps me ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not aware of any relevant third party apps that can be used with Service projects. There could be one of which I am unaware.
Adaptavist's ScriptRunner Behaviours can be used to change a field to read-only, but currently it can be used only with Software projects. The same is true for Appfire's Live Fields app.
Based on my research this is due to limitations from Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe you have a numbers of atlassian tickets, where they explain reasons of their decision about this questhion
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can confirm we are working on support for Jira Service Management projcets in Behaviours and this will be coming in 2026 and I would advise following the feature request here to see when JSM support is released for behaviours.
Kristian
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.