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
I wanted to make Assignee field read-only and only editable during particular status. I created screens for these selected status and added the Assignee field. Then I removed the Assignee field from the Edit issue screen, but kept it in the View issue screen. However, the Assignee field remains editable in all the way through the status workflow.
I've seen posting about adding step property, but I couldn't figure out how to do it.
Can you plese help?
I don't believe there are anything that you can use in step's properties to achieve what you wanted to control Assignee field. See reference link - https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/
Your action of removing Assignee field from the edit screen is correct. Now what you need to do is to create a transition window with the field and associated with your WF's status transition. You can even make the field required via the validator setup for the same transition.
This means that Assignee field population is controlled via the WF only.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
You can do this by using workflow properties to change the permissions by status, but only for a couple of fields. The trick is to understand that the assignee field is controlled by permissions, unlike most others (most fields work off the "edit" permission, which is global - it affects the whole issue, not specific fields)
You can set a property on a step in a workflow that says "no-one (or a limited set of people) has the right to assign issues", which will override the permissions in the project permission scheme.