Hi,
The addon Scriptrunner can help you with this with use of it's Behaviours feature if you are using Jira Server (Not cloud).
Find the addon here: https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview
Read more about the Behaviour feature (with examples) here: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html
Hope this helps.
Expanding Knut's answer, the Behaviours solution is fine but imho I think it is not enough (or it is incomplete) for your purpose since, as far as I remember, behaviour only apply on creation and transition screens and if the field is in the edit screen and your instance permit inline edit, restricted users will be able to edit the "read-only" fields.
One solution is to remove edit permissions to these users and create a recursive global transition called "Edit" or whatever you like just for them (you also can do it foe all the users, the scope depends on your decision) where you can apply all the behaviours with no restrictions, this will remove inline edition capacity to all users.
The other solution is to use 3rd party addons that allow you to add another security layer at fields level, you can check FSP from quisapps.com
Greetings,
Marcos.
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.