Jira Automation - Child issues inherit Epic Link from Parent

Question

Hello!

Like the title states, I am trying to set up a Jira Automation to have child issues inherit its parents' epic link.

On my team, we have an additional issue type called "New Feature", which is the parent to a group of stories. An Epic is a parent to a group of New Features. Epic -> Features -> Stories.

The scenario:

I want to move a feature, and therefore, a group of stories, to under a new Epic (the team found that it fit better under a different bucket). So I changed the parent link of the feature to the new Epic, and I changed the epic link of the Feature, but the 55 stories that we have under the feature all still have the old epic link. Do I need to go one by one changing these epic links? Or is there a way to automate that when a parent epic link changes, so does all of its children?

Thanks,

Lea

Bill Sheboy · Answer

Hi @Lea Casper

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.  Thanks!

Kind regards,
Bill

Mark Segall · Answer

Ok - In that case, you'll need some type of business logic that automation can leverage to identify the relationship between the New Feature and corresponding stories.  For example, let's say that all of the stories have been linked to the new feature as blockers.  In this case, your automation rule would look something like this:

* TRIGGER: Field Value Changed (Parent Link)
NOTE - Epic Link is not supported as a trigger, but Parent Link has proven to work instead.
* CONDITION: Issue Type = New Feature
* BRANCH (Linked Issues - Is Blocked By)* Edit Issue (Epic Link)* Copy from Trigger Issue

Lea Casper · Answer

Hi @Mark Segall

Actually, I created a new issuetype called New Feature, I think it's more similar to a Story. The epic remained the same! Epic resides above Feature and Story.