Automation Bug: Edit Field not working

[Ryan Willms]

My automation is quite simple:

When: field edited

Then: Update same field in sub-tasks

I did it this morning and it did not even trigger. The only thing I can think of is that I see a UI update (eg. "Add people", "Add date") and in classic Atlassian fashion, this has broken easy workflows.

[John Funk]

Hi Ryan,

Atlassian has an ongoing active incident with its products due to AWS issues. Are you sure the Rule even fired? Also, screenshots are always helpful - the full rule, audit log when it runs, etc. 

[Ryan Willms]

The rule is not being fired. Perhaps this is due to AWS.

[John Funk]

That's my suspicion. Are other rules firing though? Does this rule get fired as the result of another rule firing? Or is it executed directly? On other words, is the Box field updated sometimes as the result of another automation rule firing? Or is it always just when someone updates it directly on the screen? 

[Ryan Willms]

No automations are firing, and I just posted out of frustration. Seems likely it's the AWS issue - thanks for all inquiries

[John Funk]

Yep, hopefully that's it and it's back up and running soon. The good thing is that the automation rules tend to fire and catch up when down like that. Hopefully that will be the case. 

[Ryan Willms]

There is no audit log, because the trigger is not even happening, despite matching the conditions.

[Bill Sheboy]

Hi @Ryan Willms 

For a question like this, context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

As you describe it, the rule could not work: without a branch to the subtasks, they could not be accessed for an edit.

And, some field updates do not trigger the Field Value Changed trigger.  The reason is there are separate triggers for them.  For example, assignment, status transition, comment changes, work logging, etc.  Seeing your complete rule will help to confirm this.

Kind regards,
Bill

[Gor Greyan]

Hi @Ryan Willms

Could you please provide screenshot from the Audit Log of the mentioned automation?