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 Rule isn't triggering as expected

Brad H_c4tfaz

Hello,

I'm looking to make an automation role to automatically update some fields, and I've run into an issue. When two date picker custom fields are updated in an Epic, I want the changes to update to the same fields within the associated Stories and story Sub-tasks. I created these as two separate rules, and while the rule to copy the values from Epic to Stories is working, the rule to copy the values from Stories to Sub-tasks is not.

Configuration of rule copying from Epic to Stories
When: Value changes for

Committed Completion Date, Drive to Date

If: Issue Type equals

Epic

For Stories (or other issues in Epic)

Then: Edit issue fields

Committed Completion Date,

Drive to Date

Configuration of rule copying from Stories to Sub-tasks

When: Value changes for

Committed Completion Date, Drive to Date

If: Issue Type equals

Story

For Sub-tasks

Then: Edit issue fields

Committed Completion Date,

Drive to Date

The scope is set to a single project, and in the Then component of the rule is set to copy the values from the Parent Issue. I tried this with the Trigger Issue option as well, with no success. I found that if I manually update the Story, the automation rule does copy the values to the Sub-task, but I’m seeking to have one update to the fields within the Epic transfer over to the Stories and Sub-tasks. The first automation rule is triggering the second, is that where the issue is here?

Accepted answers

Bill Sheboy

Hi @Brad H -- Welcome to the Atlassian Community!

By default, the actions of one rule cannot trigger another. This is to prevent errors, such as run-away looping. Your first rule performs actions to copy fields from the Epic to the child Stories, but the second rule does not start / trigger because that is option is disabled.

To allow the second rule to trigger, please enable the "Allow Rule Trigger" option in the rule details at the top of the second rule only. Then re-test to confirm it works as expected.

Kind regards,
Bill

All comments

Kalyan Sattaluri_iinm1n

Hello @Brad H

Welcome to the community.

Can you confirm if you Epic and stories are in the same project? Stories and sub-tasks will work fine because they are in same project, but Epic -> Stories will not work if your epics are in different project than stories and you dont have permissions to expand scope.

Also, if they are in same project, please add a log statement inside your branch to show that you do have the right values. see below my modification.

Configuration of rule copying from Epic to Stories
When: Value changes for

Committed Completion Date, Drive to Date

If: Issue Type equals

Epic

For Stories (or other issues in Epic)

Then: Log {{Committed Completion Date}} & {{Drive to Date}} <-- Add this step

Then: Edit issue fields

Committed Completion Date,

Drive to Date

Once done, please share screenshot of your rule and your audit log to help.

Bill Sheboy

Hi @Brad H -- Welcome to the Atlassian Community!

To allow the second rule to trigger, please enable the "Allow Rule Trigger" option in the rule details at the top of the second rule only. Then re-test to confirm it works as expected.

Kind regards,
Bill

Brad H_c4tfaz

This was what I was missing, thank you very much for your help.

Welcome!

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

Quick Links

Find more posts tagged with

jira

automation

data-center

jira-software-data-center