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

Rule to Edit a field value for all Stories and Sub-Tasks when changed in the Epic

Dillon Scicluna

I need to create an automation for when a field value is changed in the Epic, all Stories and Sub-tasks under that Epic edit that specific field's value similar to the Epic's.

With regards to stories, I managed to make it work automatically for both Scheduled changes and Field Value changes.

However, when it comes to Sub-Tasks, I only managed to run the rule for the Value change independently from the Story rule (i.e. When both Story and Sub-Task rules run one after the other, only the Story automation works while the Sub-Task automation field value remains as it was). Also, which is very strange, unlike the Value change automation, the rule does not work when it is Scheduled for Sub-Tasks.

What can I be doing wrong when it comes to the Sub-Task automations?

Accepted answers

Trudy P Claspill

Hello @Dillon Scicluna

Welcome to the Atlassian community!

You can use a rule like this (substitute your field where I used Fix Versions).

Screen Shot 2023-01-19 at 10.51.33 AM.png

The first half of the rule will run to update the Stories when the Epic is updated. The second half of the rule will be run as a separate invocation of the rule based on the Stories having been updated.

On the Rule Details page you need to check the box for Allow rule trigger.

In the Edit Issue Fields components you need to use the Copy value from Trigger issue option.

Screen Shot 2023-01-19 at 10.54.17 AM.png

All comments

Trudy P Claspill

Hello @Dillon Scicluna

Welcome to the Atlassian community!

You can use a rule like this (substitute your field where I used Fix Versions).

Screen Shot 2023-01-19 at 10.51.33 AM.png

On the Rule Details page you need to check the box for Allow rule trigger.

In the Edit Issue Fields components you need to use the Copy value from Trigger issue option.

Screen Shot 2023-01-19 at 10.54.17 AM.png

Dillon Scicluna

Thanks for your help @Trudy P Claspill !!

The Allow rule trigger check was the solution I needed. However, I still had to create 2 automations for the rule to run on a Schedule instead of a Field Value change.

Dillon Scicluna

@Trudy P Claspill I updated the automation to run on a schedule instead of a field value change however, the sub-task part is not being updated for whatever reason. I tried with 1 Automation, and 2 automations for each: stories and subtasks (Setting the 2nd schedule slightly after just in case the fields do not change quick enough). What could the issue be, please?

Trudy P Claspill

Your original post says the requirement is "when a field value is changed in the Epic,". Why are you using a Schedule trigger instead of a Field Change trigger?

If the requirement is to do this on a Schedule, I would assume you are including a JQL in your Schedule trigger(s). Please share those details.

Andrea Pareja

Hi,

I'm trying to use this rule, but the field I want to use does not have the options 'Copy from Epic, Copy from Parent. Its 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 use the option selected in the epic to populate all child issues?

Trudy P Claspill

Hello @Andrea Pareja

A Select List (Single) should have that option available.

Did you click on the ... button next to the field and select COPY?

Screenshot 2024-04-19 at 12.26.33 PM.png

Then click on the displayed text to get the pop-up.

Screenshot 2024-04-19 at 12.28.47 PM.png

Then pull-down the Issue to copy value from field and select Parent

Screenshot 2024-04-19 at 12.29.29 PM.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

atl-gruland