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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Jira automation not picking up changes on subtasks?

Have been working for a while now with Automation for Jira and recently users started complaining about rules not being executed as expected.

Long story short- a few rules are built on Status changes on SubTask Issue type issues. 
Previously it worked as expected, but not they do not show up on Audit log for these rules even. 

Anyone experienced something similar? 

Any help is much appreciated! 


1 answer

0 votes
Jack Community Leader Feb 25, 2021

Can you take a look at the audit log for a sub-task issue transition where you feel it should execute and share your findings? If the audit is unclear we may wish to add some “log action” to the rule to capture info.

Sure- I would add something- but the logs are completely empty- changes are not being picked up by the rule. 

Hi @zilvinas_mickus 

I noticed that you selected the option Allow rule trigger in the details.  Do you have another rule that is intended to lead to this one firing?

If so, is that earlier triggering and processing as expected?

Best regards,


Hey @Bill Sheboy thank you for your time- yes, it is taken in by another rule, but that one is performing as expected.

Thanks for that information, @zilvinas_mickus 

Let's try this... These steps should rule out starting condition problems and permissions.

  • Disable the rule that has the problem/symptom
  • Clone/copy the disabled rule, changing the trigger to manual, and enable it.  Confirm the rule actor (in details) is who you expect.
  • Create a test issue, ready to trigger the rule.  (You can delete or abandon it later.)  If you have no role in the project for the rule, ask someone in the project to create the test issue.
  • Perform the conditions that lead to that first rule you note firing for the test issue. You should now be in a starting point that would lead to the problem rule not firing
  • Stop and look around to confirm what you expect for entry conditions in the test issue
  • Now run the cloned rule manual and see what happens

Best regards,


Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

124 views 3 14
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