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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,397
Community Members
 
Community Events
176
Community Groups

Making fields required with assignee

Hello, 

The field "component" is not applicable to all teams on our project and I would like to make the components field required for select team members.  

Are there any ideas for me to do this?

I was thinking I could do this in in automation rules, but there doesn't seem to be a way to trigger this?

Thanks

1 comment

Hi @Stacey 

In Jira, fields can be configured based on the project & issue type pair, and I'm not aware of any other way to configure their mandatoriness for a specific project role or group of users only.

Also Automation doesn't seem to be of help here either, as it works after the issue is created, and not on the create issue screen directly.

Comment

Log in or Sign up to comment