How long do automation rules take to update sub-tasks?

[Ann Rumenapp]

I have an automation rule to change all Epic child cards and their associated sub-task cards when the Epic changes either the project or work type (custom) fields. The audit log shows the sub-task cards as updated but the cards do not reflect the changes 10 minutes later.  Have others seen this delay?  If so, what amount of time did it take to change the sub-task card fields?

[Mikael Sandberg · Accepted solution]

The update should be immediately after the automation has run. What does your automation looks like?  

[Ann Rumenapp]

History - this morning the rule was working and showed results immediately.  This afternoon the rule runs, audit log says it successfully updated the card but the card does not show the changes.

This tool won't let me paste a picture so here is the rule:

When Issue Created

Issue type is one of : Story, Task, Sub-task, Spike, In-Sprint Defect task, Bug, SecurityRisk, Dependency Task, Technical Debt, Production Support, Improvement

Then Edit issue fields

Work Type = Copy Work Type from Parent issue

Project = Copy Project from Parent issue

---

Audit Log shows rule runs successfully

Date      Rule       Status   Duration              Operations

10/19/23, 12:39:51 pm (22645745475)    Set project and work type on issue create             SUCCESS              1.14s     

Show more

10/19/23, 12:39:15 pm (22645722993)    Set project and work type on issue create             SUCCESS              1.24s     

Show less

Action details:

Issue condition

The following issues passed:

ALC-4982

Edit issue

Issues edited successfully

ALC-4982

---

Card does not show either field as changed - please tell me how to take a screen print and add it here so you can understand the challenge

[Mikael Sandberg]

To take a screenshot on Windows 10/11 press Windows logo key + Shift + S, on MacOS press command + Shift + 4. You can then use the Insert photos button to add it here.