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

How can I create an automation rule trigger to run when ANY jira field is updated

Hi There, and thanks in advance for responding if you know the answer. 

I'm trying to create a Jira automation rule to trigger whenever any field is updated in an issue.  

My workflow: user submits a request, support team receives the ticket and sends it to another team to work off.  I have automation  set up to manually clone the issue from parent to child projects to maintain visibility but now I would like the child to parent cloning to happen automatically and not manually.  

Is this possible?  And if so, how should I configure the trigger?  

Thank you in advance. Olga

1 answer

1 accepted

1 vote
Answer accepted

Hi @Olga Toverovskaya,

There is an issue updated trigger available. Check out Automation for Jira DC/Server documentation and scroll down to find the issue updated trigger.

You can specify a JQL condition further on to limit the selection of issues to apply further actions on.

Hope this helps!

@Walter Buggenhout _ACA IT_ , thank you for the lovely idea!  This "when to run the rule" part of the JQL query works beautifully with the when issue is updated.  How do I next say to update all the fields in the linked (parent) issue?  Please say there's a magic trick for that too!  

If you want to do something on the child issues when the parent issue is updated, you could extend your rule and add an "Issue branch" on all linked issues when the issue is updated.

That way, you can add actions on the child issues when the parent issue is updated

Like Olga Toverovskaya likes this

Suggest an answer

Log in or Sign up to answer

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