We need to be able to lock specific fields without disabling the user's ability to edit comments and status, etc.
Possibly, depending on when you want this "lock" to occur.
You can remove the field from the "edit" screen, but that removes any ability change the field in general - your users will only be able to change it during transitions.
Editing (and creating) comments is unrelated to screens (have a look at the permission scheme for the progect), and the ability to change status is controlled by conditions on your workflow.
Hi Brittany
JIRA doesn't have field level permissions per se. The only way I know of protecting a field from editing is to leave it off the edit screen. Then, you would create loopback transitions to each status (a transition that ends in the same status). On that transition, you could set your permission condition and expose the field on that transition screen.
Hi @Nic Brough -Adaptavist- - Does this prevent the user from updating the field using the Bulk Edit feature?
If you want to create instructions, use a message field. Message fields don't ask for input - just give information. They can be for Edit (visible in Edit screen) or View, and accept HTML.We use it at the top of a tab or transition screen to give instructions or a link to documentation for a process.
It would be great to really be able to lock a field from edits. We noticed that even though the field is not on any edit screen that the user has access to. If they load up the issue in Jira Plan (previously Advanced Roadmaps) then they can actually edit the content. Hopefully a user would not go to this effort but now easy for a PM / Scrum Master to accidently break something due to this.
It looks like you're new here. Sign in or register to get started.
