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

Automation Epic Link to Linked Issues

Neta Knyazhansky Caspy

Hello,

In my teams' project we have Epics with Stories, Tasks are set as linked issues to the Stories, as they can't be children of Stories.
I'd like to configure an automation for Tasks to have the same Spic link as the Stories they're linked to.

Anyone can please help with that?

Thanks!

Accepted answers

Mark Segall

Hi @Neta Knyazhansky Caspy

The big thing with the link is that you'll need to identify whether the Task is the current issue or destination issue.

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

So if Task is the Destination Issue it would look like this:

TRIGGER: Issue Linked
BRANCH (Destination Issue)
- ACTION: Edit Issue (Epic Link)
- {{triggerIssue.Epic Link}}

If its the other way around, it would look like this:

TRIGGER: Issue Linked
ACTION: Edit Issue (Epic Link)
- {{destinationIssue.Epic Link}}

One last note... This is assuming the project is a company managed project. If you're using a Team managed project, replace "Epic Link" with "Parent".

All comments

Mark Segall

Hi @Neta Knyazhansky Caspy

The big thing with the link is that you'll need to identify whether the Task is the current issue or destination issue.

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

So if Task is the Destination Issue it would look like this:

TRIGGER: Issue Linked
BRANCH (Destination Issue)
- ACTION: Edit Issue (Epic Link)
- {{triggerIssue.Epic Link}}

If its the other way around, it would look like this:

TRIGGER: Issue Linked
ACTION: Edit Issue (Epic Link)
- {{destinationIssue.Epic Link}}

One last note... This is assuming the project is a company managed project. If you're using a Team managed project, replace "Epic Link" with "Parent".

Neta Knyazhansky Caspy

Hi @Mark Segall

If I understood correctly, then the Task is the destination issue, as I'm to make it "inherit" the Epic Link from the linked Story.

This is the configuration I came up with, yet it's not working, any advice?

Mark Segall

Hi @Neta Knyazhansky Caspy - Issue/destinationIssue is determine by the link type. If the task "child" of the Story it will be the "issue". If the task is "parent of" the story it will be the "destination issue".

It is purely based upon what link type has been assigned which can be a little weird to wrap your head around at first.

To double check this, I would add a Log Action to your rule just before the branch.

Issue = {{issue}} || Destination = {{destinationIssue}}

This will log the two values to the rule audit log so you can be sure about whether you need to branch into the destination issue or work directly against issue.

Neta Knyazhansky Caspy

Thank you!!

Working perfectly

Manny_hsdwu7

how to do this for existing linked issues? we have tasks linked to story and want to copy the epic link value to the linked tasks from the story, not able to figure out a way to do this for existing issues

Neta Knyazhansky Caspy

Hi @Manny

For an automation to run, you need a trigger. If there's a certain trigger you can run on all these tasks, then just add this step to the suggetion above, then run it.

If not, I'd suggest using bulk edit to add the Epic link.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation