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

Need help with an automation logic

Priyanka Agrawal_nef1a1

How to write an automation in jira such that If a story’s start date is updated, the automation should update Epic’s start date to the earliest start date of all the stories linked to the Epic. Additionally, if a story is removed from an Epic, the automation should update the Epic’s start date based on the remaining stories linked to the Epic.

I managed to write an automation (and it is working as expected) for the linked stories but could not write a logic for when a story is removed from an Epic. Kindly help.

Accepted answers

Trudy P Claspill

Hello @Priyanka Agrawal

Welcome to the Atlassian community.

For the case where an issue is removed from an Epic you would need to start with the Field Value Changed trigger and monitor the Parent field.

With that trigger you get access to the {{fieldChange}} smart value, which allows you to access the value of the field before it was change and the new value of the field. Refer to:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

Using those values you can create a FOR JQL branch to change focus to the previous Parent Epic and execute the steps to change its start date.

You can also use the steps you have in your first rule to update the start date for the trigger issue's new Parent Epic.

Vishal Biyani_2pr07j

@Priyanka Agrawal

To make the update work from StandardIssue -> Epic -> Initiative, see below

instead of using portfolioChildof need to use triggerIssue to reach the Initiative key from Standard Issue

Hopefully it will work in your use case.

Thanks a lot @Trudy P Claspill for your insights.

All comments

Trudy P Claspill

Hello @Priyanka Agrawal

Welcome to the Atlassian community.

For the case where an issue is removed from an Epic you would need to start with the Field Value Changed trigger and monitor the Parent field.

With that trigger you get access to the {{fieldChange}} smart value, which allows you to access the value of the field before it was change and the new value of the field. Refer to:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

Using those values you can create a FOR JQL branch to change focus to the previous Parent Epic and execute the steps to change its start date.

You can also use the steps you have in your first rule to update the start date for the trigger issue's new Parent Epic.

Priyanka Agrawal_nef1a1

Could you please help me know in detail, how can I use {fieldChange}} smart value? At which step?
Can I add this clause to my current automation? Or would this require a new rule?

Trudy P Claspill

You need a separate rule to monitor for a change to the "Parent" field.

You can make a copy of the existing rule as a starting point, and change the field monitored in the Trigger to Parent. The structure you have would then handle the update of Start Date for the issue's new parent Epic.