Automation rule to populate tasks and sub-tasks of epic children when Epic changes

[Ann Rumenapp]

Looking for some automation rule help - I have a rule for when an Epic change 2 custom fields (Project & Work Type) then populate that value on all the Epic children.  My rule won't populate the sub-tasks though.  Suggestions on how to make the rule work for all Epic child cards & Sub-tasks?

Here is the rule that partially works:

[Adam Rypel _MoroSystems_ · Accepted solution]

Hi @Ann Rumenapp ,

As it seems your branch searches only for stories, try using JQL branch and using JQL "parentEpic = {{issue}}". The parentEpic function looks for all the tasks in the epic and their subtasks.

[Ann Rumenapp]

THANK YOU so much!  That worked.  I'm just learning/testing out how to write automation rules.

[Ann Rumenapp]

Do you have a link to Atlassian documentation on branch search function options?  I have another rule to update a card and it's sub-tasks that there is probably a function for

[Adam Rypel _MoroSystems_]

Good luck! Automation is fun. 

The whole documentation for JQL is here https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/ . If you want to see the exact options, check out functions and fields section.

[Ann Rumenapp]

I'm not enjoying this assignment for automation rules at all!  I get one rule to work and then other rules conflict.

[Ann Rumenapp]

Hi @Adam Rypel _MoroSystems_,

Today when running the automation rule, the audit log gives me this error on subtask cards: No fields or field values to edit for issues (could be due to some field values not existing in a given project)

I've checked the screen and field configurations which have the work type and project fields.  Where else should I look to figure out this error?

[Adam Rypel _MoroSystems_]

@Ann Rumenapp apologies, I missed your response.

I would also check the custom field context - it can be limited only to the Epic and not subtasks.

[Andrea Pareja]

Hi @Adam Rypel _MoroSystems_ 

I'm trying to use this rule and your suggestion, but the field I want to use does not have the options 'Copy from Epic, Copy from Parent. ' This field's type is Select List(Single), so it just allows me to select from one of the defined options. 

Do you know any other way to take the option selected in the epic and populate all child issues with it?

[Adam Rypel _MoroSystems_]

Hi @Andrea Pareja 

I tested it on select list and it works for me.

You need to first click on three dots and select copy:

Then click on "Copy customfield from Current Issue" and change the Issue to copy value from to the issue you need: