Anyone is able to edit a custom field that is restricted by behaviours to Read only or Hidden. This happens when you first open the JIRA Issue or after a refresh. When you change another field on the ticket it will start working again but all it takes is a refresh to give you the ability to edit the custom field again.
JIRA Server: 7.1.10
ScriptRunner for JIRA: 5.0.4
Here is the JIRA Issue:
Here is the Behaviour Mapping:
Here is the Behaviour Settings:
Hey Tools Admin
There is a bug in our backlog that closely resembles what you have stated. The team and I have been taking a look at this today. We are unable to reproduce the exact behaviour you mention, so if you would be so kind as to give us directions on how to reproduce it in this ticket we could help you further.
Thanks a lot, if we can help you with anything else don't hessitate to ask.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot