Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Jira Automation - Child issues inherit Epic Link from Parent

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

 

 

 

1 answer

1 vote
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 03, 2023

Hi @Lea Casper - To make sure I understand this correctly, You have renamed the native "Epic" issue type to "Feature" and created a custom issue type called "Epic".  Then you updated the issue type hierarchy so that Epic resides above Feature.  If this is correct, you do not need to do anything with the child stories.  If you change the parent link of the Feature, all of the children will dynamically follow it to the new Epic and this would be reflected on any Advanced Roadmap Plans

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.

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 04, 2023

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
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 04, 2023

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events