nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Syncing comments from the Epic to the child tickets is not working

Nguyen Thanh Tien

I have set up an automation to sync comments from Epic to all child tickets, as shown in the attached image.

iScreen Shoter - Google Chrome - 250210103220.jpg

However, I've encountered an issue where some tickets are not syncing. The audit log displays the message: "No related issues that have been updated since the last time this rule executed could be found. To include all issues, un-check the 'Only include issues that have changed since the last time this rule executed' checkbox."

iScreen Shoter - Google Chrome - 250210103204.jpg

I cannot find this checkbox mentioned in the audit log. Could you please assist me with this issue? Thank you!

Accepted answers

All comments

Vishal Biyani_2pr07j

@Nguyen Thanh Tien

Can you try adding Re-fetch issue data action and see if this helps resolve your problem?

Mohanraj Thangamuthu

Hello, Good day. Check whether "Prevent" duplicates option has been enabled in the rule action.

Screenshot 2025-02-10 at 10.50.38 AM.png

Nguyen Thanh Tien

The checkbox you mentioned has been checked, but the issue is still occurring.

Nguyen Thanh Tien

The issue still persists

iScreen Shoter - Google Chrome - 250210140229.jpg

Mohanraj Thangamuthu

Hello, Good day. Please un-check the "Prevent duplicate option" and check the status.

Also the option mentioned in your description will be available on the trigger if we use scheduled rule, but from the screenshot its not scheduled rule.

Screenshot 2025-02-10 at 12.33.59 PM.png

Nguyen Thanh Tien

I've unchecked the checkbox, but the issue continues to occur with the same message is still appearing in the audit log "No related issues that have been updated since the last time this rule executed could be found. To include all issues, un-check the 'Only include issues that have changed since the last time this rule executed' checkbox."

iScreen Shoter - 20250210141528697.jpg

Vishal Biyani_2pr07j

try adding re-fetch issue data after the check for Issue Type equals Epic

Vishal Biyani_2pr07j

@Nguyen Thanh Tien

This is how the rule should look

Nguyen Thanh Tien

I do not know why, but the issue was resolved when I changed the branch type from 'children' to 'stories (or other issues in Epic)'. Thank you all @Vishal Biyani @Mohanraj Thangamuthu for taking the time to advise me on this matter!

iScreen Shoter - Google Chrome - 250210171821.jpg

iScreen Shoter - Google Chrome - 250210172240.jpg

Vishal Biyani_2pr07j

Good to know that it finally worked!!!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud