I need help with automating the update of a parent Epic's status color based on the status colors of its child work items. Here's the logic I want to implement: * If all child work items have a status color of "TBD," then set the Epic's status color to "TBD." * If any child work item has a status color of "Red," then set the Epic's status color to "Red." * If any child work item has a status color of "Yellow," then set the Epic's status color to "Yellow." * If any child work item has a status color of "Green," then set the Epic's status color to "Green." Could someone guide me on how to achieve this via automation? Trying to explore more reliable methods to handle this to ensure it doesn't fail.

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 Lookup all the child items values and then update the Parent

Sam Lin

I need help with automating the update of a parent Epic's status color based on the status colors of its child work items. Here's the logic I want to implement:

If all child work items have a status color of "TBD," then set the Epic's status color to "TBD."
If any child work item has a status color of "Red," then set the Epic's status color to "Red."
If any child work item has a status color of "Yellow," then set the Epic's status color to "Yellow."
If any child work item has a status color of "Green," then set the Epic's status color to "Green."

Could someone guide me on how to achieve this via automation?

Trying to explore more reliable methods to handle this to ensure it doesn't fail.

Accepted answers

Trudy P Claspill

Hello @Sam Lin

Are the above conditions in priority order? If once child issue is Red and another is Yellow, should the parent be set to Red?

When do you want this rule triggered? Should it be triggered when the color changes on a child issue? Do you need this to run periodically against a set of parent issues?

What is the subscription level for your Jira subscription; free, standard, premium, or enterprise? I ask because there are limitations on how many rule executions you can have in a month based on your plan. That may impact the recommendation about the type of rule to be developed.

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

All comments

Trudy P Claspill

Hello @Sam Lin

Are the above conditions in priority order? If once child issue is Red and another is Yellow, should the parent be set to Red?

When do you want this rule triggered? Should it be triggered when the color changes on a child issue? Do you need this to run periodically against a set of parent issues?

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

K Vivek Rao_y5kp3p

Hi @Sam Lin ,

Just to confirm before we proceed — when you mention 'status color' (Red, Yellow, Green, TBD), could you specify where this value is stored on the issue? For example, is it: (1) the issue Status itself, (2) a custom field, or (3) another attribute like a label or component? This will help ensure the automation is set up correctly.

Also, is it on cloud or DC?

Sam Lin

Hi @Trudy P Claspill , thanks for your response.

The conditions should follow a priority order—if any child issue is marked Red and others are Yellow, the parent should be set to Red.
Currently, I’m able to run and configure this rule based on changes to the status color field for issues under the Epic.
Our subscription level is Enterprise.

Thanks again!

Sam Lin

@K Vivek Rao

The data is stored in custom field and currently on the Cloud.

Thanks!

Trudy P Claspill

I think I have this worked out, but it is late and I need to test it before saying it is a working solution.

The basic idea is to run a series of Lookup Issues actions to look for sibling issues matching each "Color" value and set a variable to the number found.

Then run an If-else block where you first check the value of the variable counting the TBD siblings found and set a Color variable to TBD if that is greater than 0. Set of the Else-if blocks to check each of the other variables created after each of the other Lookup Issues action, and set a shared Color variable to their color if the counting variable is greater than 0.

The idea is at the conclusion of the if-else block you have a "Color" variable that is set to the color you want to use in the parent issue.

I need to test if this actually works. After testing tomorrow I'll post another reply.

Sam Lin

@Trudy P Claspill Thank you looking forward for your suggestion.

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

jira-automation

cloud-automation