Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How can I make Assignee read-only

Zaldy Parian
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 27, 2023

Hi all,

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?

 

Regards,

2 answers

1 vote
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 27, 2023

@Zaldy Parian -

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

Viasat Inc.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 12, 2023 • edited

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events