I'm trying to restrict custom field "Story Points" editing to few and should be read-only to all other users.
For this, under behaviors, created a behavior >> mapped to required project >> under field selected "Story Points" >> and added exception to be written for few users.
By doing so I was able to make it read-only for all users except the users I mentioned in the condition. But the inline editing is still accessible to all the users. How to fix that?
Can we use script conditions for each transition? If so, can you help in improving the script?
def storypoints = getFieldById("Story Points")
In my example I used summary field but you can change it to Story Points.
I marked field as read only and set negative condition wich allows users from group jira-administrators to edit summary field.
I hope that this will help you :)
Hi @Sebastian_Krzewiński , thanks for the response.
In this context what was your screen configuration? Does the field summary included in the edit screen? I think screen config. is overwriting the behavior setting.
This is my setting. What's happening is, it is read-only for all the users except the one I mentioned in the condition, only in the edit screen. Still inline editing is enabled for all the users.
I had same issue.
I think it is linked to your ScriptRunner version ?
When trying to edit a field that is linked to a Behavior, the Edit form should come up, you shouldn't be able to do inline edits on such fields (see Scriptrunner Behavior doc).
Unfortunately it seems there were some versions of Scriptrunner with a bug : inline editing was allowed even for Behavior linked fields....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events