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; } } }

Automation Q - Sync Team Field: Parent to Child

Claudia

Hello Atlassian Community,

This is one of my first automations I have ever created for my company and I really need help.

Automation Intended Outcome: When an issue is created or updated, automatically populate the "Team" field on all child tickets when the "Team" field is filled out on the parent ticket.

I have created two separate automations:

1st automation - for when an issue is created

2nd automation - for when an issue is updated

Neither automation is firing right now, so I'm curious what I am doing wrong. Any help is greatly appreciated!

Issue Created 2025-02-12 at 1.46.26 PM.jpg

Issue Updated 2025-02-12 at 1.46.40 PM.jpg

Accepted answers

All comments

Bill Sheboy

Hi @Claudia

Please post an image of the audit log details, expanding all of the sections / dropdowns. That will help provide context for what is happening.

Until we see that...

You describe wanting to update the Child issues when the Parent's Team field changes.

Then condition to test if the Parent exists is not needed because the intended trigger is the Parent, correct?

You could create an additional rule (for Child issues) in case someone manually changes the Team field, allowing it to be reset back to the Parent's value.

Kind regards,
Bill

Claudia

Hi Bill,

Thanks for getting back to me! Here are the expanded audit logs for both automations:

Issue Created Automation
Issue Created 2025-02-12 at 3.20.46 PM.jpg

Issue Updated Automation Issue Updated 2025-02-12 at 3.21.36 PM.jpg

Bill Sheboy

Thanks for those images, and let's focus on one rule at a time, starting with the Issue Created one.

First, when using the Issue Created trigger, always add the Re-fetch Issue action immediately after the trigger. The reason is that trigger can fire so quickly that some of the issue data may not be available to the rule yet...causing problems later. The re-fetch will slow the rule a bit and reload the data before proceeding.

Next, please remove that Parent condition I noted earlier.

Looking at the log, VPMPROJ-704 did not have a value for the field, causing the condition to fail. Does that sound correct? If not, it may have been caused by the missing Re-fetch action I noted earlier.

Please make those changes, and then re-test your "created" rule.

Also please note: both of your rules have the same trigger, Issue Created. Did you want the "updated" one to instead use the Issue Fields Updated trigger for the Teams field?

Claudia

Focusing on the issue created rule, I removed the parent condition and added the Re-fetch issue action. This is how it is now set up.

When I went to re-test, the Team field still wasn't being populated.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation