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
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
When I create an issue, all values can be changed anytime.
Is it possible to lock specific fields on given condition?
E.g. we have larger workflow to manage issues.
At the first section of this workflow, full editing is welcome. Upon a specific status (e.g. approved) some field shall be unavailable for editing, but shall be visible in the issue.
I've seen following "possible" solutions:
Is there another approach available to lock fields?
On cloud and on Jira software you can't lock field on conditions. You either place them on the create/edit screen (for users to edit them), or you don't.
If you want these fields to be on the created screen, then you should work with validators, to ensure that a specified condition should exists (e.g. user belongs to a certain group, or on a specific role).
Another thing you could do is:
Doing the above will ensure that only certain users can use the above transition, meaning that only certain users can edit these fields.
On Jira cloud, there isn't a "field locking" permission. If you were on prem Jira, you could lock them using scriptrunner, but again you had to write some script.
You can add the self transaction on each stratus and add the transaction screen on that self transaction with those field which you want to edit on that transaction screen.
For example - On In Progress Status you can add transaction from In Progress to In Progress and attach the transaction screen to that transaction and mention field which you want user to edit.
Accept the answer if it helps