You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
Cheers:
DYelamos
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.