Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Making a field mandatory using automation rule

Good day 

Is it possible to make a field mandatory when setting up an Automation Rule on a Project. I have setup the Trigger and Condition on the Automation Rule but do not see an Action to make another field mandatory.image.png


3 answers

1 accepted

1 vote
Answer accepted
Jack Community Leader May 21, 2021

Automation is an “after the fact” tool so it cannot be used in this manner. And Company manage projects you can use the workflow conditions and validator‘s to accomplish this type of task. 

Thanks Jack. 

Hi @Kasturee 

Are you asking how to make a field required during issue creation, or after creation make a different field required?

I do not believe that automation rules can do either of these things...

  • Fields can be made required globally for all projects, or using a validator in a workflow
  • After the automation trigger has detected the created issue, it is already created: you cannot retroactively make a field required
  • And I do not believe there is a way yet to modify a workflow from an automation rule

Best regards,


Thanks Bill. It is during issue creation that I want to make a field mandatory based on another field having no information captured. I do understand that this can be done via the workflow validator but it does not look a standard feature and may need to be done via an add-on I am assuming. 

On Jira Server, we currently use "Behaviours" to do this but I need to replicate this in our Jira Cloud Test instance

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

321 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you