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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Impossible to updating required field value on issue creation?

Hi all, 

I've run into the following issue and wondering if anyone has ideas how to overcome it:

Use case: on creating (or editing) an issue, I want automation to listen for the user changing a mandatory radio button field, and once it is being changed, I want automation to take the value of a number field A, and populate another number field B with it.

In my tests I faced the following:

1. this calculation cannot trigger before the issue is created

-> acceptable to calculate upon submitting an issue creation (and not applicable on edit as the issue exists), we can document that.

2. this calculation does not trigger/execute because before it comes to that, Jira throws an error of field B being required, before Automation can populate it.

-> is there a way to give Automation priority over the "required" field check?

-> any other ideas?


Thank you all in advance!



1 answer

1 accepted

0 votes
Answer accepted

The way Automation works, it's impossible!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events