It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restrict field edit to certain users Edited

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")

if(currentUser.name("username")){
getFieldById("Story Points").setReadOnly(false)
}else{
getFieldById("Story Points").setReadOnly(true)
}

1 answer

Hi @Sarath 

 

Check this:

Screenshot 2019-10-02 at 23.08.55.png

 

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 :)

 

Regards,

Seba

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.

behavior.PNG

Hi @Sarath 

 

My configuration block summary field on edit screen.

Behaviours works only on create and edit screens so you can't achieve described action (block inline edit on view screen).

Like Sarath likes this

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....

Hi @Marc Minten -EVS- the current version we're using is 5.59. Do you know if it is the version problem or just the script runner limitation on not able to to get impact on inline editing?

We are running 5.5.9 and everything is running fine. We upgraded (Adaptavist support info) to overcome the in-line edit issue.

I think you best contact Adaptavist support...

Like Sarath likes this

sure will do. thank you @Marc Minten -EVS- 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

334 views 1 3
Join discussion

Community Events

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

Events near you