Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×We need to lock down certain fields after they hit authorize in normal Changes, and make certain fields read-only when we create Standard change templates, and are struggling to do so. We found scripting for Jira, but it doesn't seem to work in JSM. Would like to know how others have solved for this.
Welcome to Atlassian Community!
JSM/Jira doesn't have field level security out-of-the-box, so you would need an app from the Marketplace in order to do this. I know that you can do this with Scriptrunner, but there are also other apps that only deals with field security.
I respectfully half-disagree with Mikael on this answer. Jira does indeed have an out-of-box solution to field security but not to the individual field level.
Let me explain, you can use Jira workflow properties to prevent certain users from updating all fields based on status of a ticket. I know that isn't the same as select fields but it may be a solution if adding comments once submitted is good enough for those impacted.
The other solution may be to have dedicated Screens based on workflow status so that once the ticket is submitted, the edit/view screens have the field removed altogether so that the data is only available to users via filter reporting.
Good luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.