Is there a way to auto label Stories based off their parent Epic?

[Rich Evers]

To help filter our work, we are wanting to label Epics.  However, when you use the label filter on the roadmap, it will only pull up the Epics and won't show the associated Stories... unless the stories have the same label.  Is there an automation rule which will auto assign a label to a Story based off its parent Epic?

I'm using a scrum board in Jira NextGen.

[michelle.bautista]

Rich's recommendations worked for me. It took a few seconds for the labels to populate but it did. Thank you. 

[Bill Sheboy]

Hi @Rich Evers 

You note using a team-managed (formerly called nextgen) scrum board...and have tagged this question with Jira Server.  Are you using Jira Server/Data Center or Jira Cloud?

Both versions could do what you ask with an Automation for Jira rule.  For Jira Cloud, this is built-in and for Jira Server/Data Center it would be either a free or paid addon...depending upon which automation features you need.

Kind regards,
Bill

[Rich Evers]

Hi @Bill Sheboy thank you for reaching out.  We are using Jira Coud.

Thanks in advance!

~Rich

[Bill Sheboy]

Thanks, Rich.  Please look here for information about the Server versions of automation rules.  https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html

Your rule would basically be something like this:

• trigger: field value changes for labels
• condition: issue type is epic
• branch: on the child issues in the epic
  • action: edit labels to set them to the triggering issue

That will keep the labels in synch.  The rule would be much more complicated if it is possible for the child issues to have additional labels than exist in the parent epic...although that might create problems for your use case and roadmap filtering.

[Rich Evers]

I can't seem to get it to work.  Here's some screen shots...

Thanks in advance!

[Bill Sheboy]

Rich, you selected the wrong branch type.  Please select the one for the stories/other issues in the epic.

Thanks,
Bill

[Rich Evers]

Still doesn't work.

[Bill Sheboy]

That is curious...Would you please post an image of the audit log details, showing an execution which does not work as you expect?  Thanks!

[Rich Evers]

[Bill Sheboy]

Thanks for that image, Rich.  Let's try a couple of other approaches:

In my experience, sometimes the rule editor "glitches" a rule from too many edits of existing components, like the branch.  A way to check that is to disable this rule, and recreate it from scratch to see if that fixes the problem.  If it does delete the disabled one.

If that does not help, you could change the branch to use JQL to explicitly find the linked child issues with:

"Epic Link" = {{triggerIssue.key}}

And just to confirm: are all of the child issues you expect for this epic in the same project, MARGTM? 

[Rich Evers]

Bill,

I tried all of the above and still doesn't work.

Yes, all within the same project.

Regards,

Rich

[Bill Sheboy]

Rich, if none of those worked it appears there is something up with the issue linking, epic to children, in your instance.  I recommend working with your site admin to submit a ticket to Atlassian Support to see what they suggest as next steps: https://support.atlassian.com/contact/#/