When and How (for automations): Epic link will be replaced with Parent

[Ilinka Danova]

Hey community,

I noticed the below warning on automations recently.

Epic Link will soon be replaced with Parent. Update to Parent field to prepare for these changes.

I've been struggling to find more information about this.

• When is this change coming into effect?
• How exactly is it going to affect automations in specific?

I found some information that for views, searches, saved filters and such the change should be seamless. However, I've found nada about automations and I'm worried I'd have to go through all automations and update this? Really hoping that's not the case but can't seem to confirm it on my own.

[Trudy Claspill · Accepted solution]

Hello @Ilinka Danova 

Welcome to the Atlassian community.

Refer to this document:

https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/#Updates-to-automation

You will not need to go back and change all the rules that currently use Epic Link.

[Ilinka Danova]

Thank you so much for sharing the article!

[Jeremy Stafford]

It says that basically everything should be moved over, however any new automations I make that check for when the epic name contains 'foo bar' they are not triggering. I've also tried with description contains.

[Trudy Claspill]

Hello @Jeremy Stafford 

Epic Name is not the same as Epic Link/Parent.

Epic Name is a separate field that was used only within Epic type issues.

Can you provide the details of your automation rule and explain what event you expect should trigger it, and the details of steps where you are referencing Epic Name?

[Jeremy Stafford]

Neither Epic Link nor Parent were in the list. I'm triggering on issue edit, and trying to update a priority when the epic name contains the phrase 'unplanned work' (issue fields condition). I've tried epic name and epic description with no luck. I looked at Epic/Theme but it only allows me to choose from a pick list, and I'm not even sure where the values in that list are coming from.

At the end of the day, I simply want to set the priority of any issues that are added to epics whose name contains 'unplanned work'.

[Trudy Claspill]

Did you already have a working rule that has stopped working since the updates concerning Epics? Or are you trying to construct a new rule?

In either case, to ensure maximum visibility to get you timely help, I strongly recommend that you start a brand new post. The only people seeing your additions to this post are the original post author and people who are watching it.

In the new post please provide screen images showing the rule you have constructed, and then an explanation for what you want to accomplish with that rule.

You said above you want the rule to run when issues are added to the Epic. Issues can be added to an Epic when the issue is created or at a later date, so clarify which of those conditions you want to accommodate.

Also, are the issues all in the same project?

And is the project involved a Company Managed project or a Team Managed project?

[Jeremy Stafford]

I can open a new post. These would be new rules, I actually have two rules (neither of which works), one on create and one on edit to cover those cases. It is a company-managed project and all issues that I'm trying to target are all in this project.

[Jeremy Stafford]

https://community.atlassian.com/t5/Jira-Software-questions/Rule-based-on-epic-info-not-being-applied/qaq-p/2615403