Trigger Rule to Retroactively populate field in child issues from parent (epic)

[Orla Mears]

Hi all, 

I've created a Trigger rule which would inherit and populate a "Feature Team" field from our parent (Epic) issues.  The child issue types would be "Tasks/Stories/Bugs" and I only wanted this to run on specific projects.

Here is what I created:

1. Scheduled trigger - specified date/time and frequency for running the trigger

2, Then: Edit Issue Fields - which I have set to "Feature Team"

3. Within the "Additional Fields" section, I had previously entered  {{issue.parent.Feature Team}}

4. I specified the projects which I wanted this to run on and updated the rule.

I ran the rule this morning and the error message I got was "Error while parsing additional fields. Not valid JSON."

5. Went by other recommendations to change this to {{issue.parent.customfield_12345}} (but put the correct custom field ID in) 

However two messages return - first is that a number of the issues passed (but I don't see the feature team showing on the child issues) and the other is the same "not valid JSON -

I hope someone can provide me with the correct configuration of the rule so I can run it and retro-populate the field on child issues from parent!

Thanks for any help

[John Funk]

Hi Orla,

A few questions. What type of projects are these? Are the all Company-managed projects? All Team-managed? A mixture? 

What type of field is the Feature Team field? Short text? Single select? Other? 

Instead of using the Advanced JSON, have you just tried to select the field? 

Finally, can you share a screenshot of your actual rule? 

[Orla Mears]

Hi @John Funk thanks for the reach out!

Yes these are company managed projects only
Feature Team field is  "Select List (Multiple Choice)"

 I've run the latest rule as  recommended via Atlassian AI - The JQL query in full is:

issuetype IN ("Task", "Story", "Bug") AND "Feature Team" IS EMPTY AND "Parent" IS NOT EMPTY

[Orla Mears]

@John Funk Here is the other option that I tried. I also as mentioned above opted for both {{issue.parent.Feature Team}} and the custom field command you'll see in the screenshot

[John Funk]

So, in the second screen shot, I see the Feature Team field. Click the 3 dots to the right side of it and select Copy. Then click the resulting value and change from current issue to trigger issue. You don't need the More options.