Hello, i need to do it in Jira cloud, tried via automation but it does not work, someone telling me to do it via scriptrunner, but hard to find information for scriptrunner cloud usage.
Hi Alex,
There are no granular permissions for field editing in the exact way that you are looking for. However there are ways to do it with Jira without using additional addons. You can create a transition to self, one that loops back into the same status. You can also
-Create one that loops back from any status to any status, so it will be available independently of the current issue status.
-Then, create a transition screen with the fields that you want to be editable by specific users.
-In the workflow set a transition condition for your new transition so that only those users can action it. Then associate it to your new transition screen.
-Finally, make sure that you have a screen associated to the edit action and remove the fields that you don't want edited from it.
This is a very summarised way of doing it. I have a post with more detail on how how to achieve this on linkedin, if you are interested.
Let me know if you want to try this and need more help to execute.
Cheers,
Diogo
Just to add, there are other ways of doing this. With automation, for example, you can set a rule that if the fields were edited by someone that is not in a certain group then automation reverts it back to the previous value. This is not really preventing an edit, but in the end it would restrict any lasting change of the value to the users you want. With automation you have the added bonus of being able to add a comment to the trigger user explaining why they are not allowed to edit it, if you wish.
This option is less onerous on the admin site, but less tidy on the frontend.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for answer Diogo, in my screenshot i tried to make this automation that didnt work, whats wrong is there? should i make this custom field "read-only"? Will try to do it via transitions way if this one not gonna work properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
{
"fields": {
"customfield_10157": "{{issue.customfield_10157.previousValue}}",
"customfield_10158": "{{issue.customfield_10158.previousValue}}"
}
}
this code for returning previous value doesnt work, maybe you know what i can do with it?
getting this error: (Specify a valid 'id' or 'name' for Internal Severity (customfield_10157), Specify a valid 'id' or 'name' for External Severity (customfield_10158))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Ivanov
To do this with automation you can use an approach that does not require JSON. Check the screenshots below for an example rule you could use (replace the field name 'Agent' by your custom field name),
Detail view of the actions
Result
Issue history
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.