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 to create an epic linked as "related to" another epic

Julieta Dienstmann

Dear All,

I've created an automation that, as soon as an Epic reaches "Done" status, if the field "component" meets a certain value, another Epic will be created.

It's working. However, I need this automation to also relate the new epic to the one that triggered the automation.

I tested this with the following automation, it creates a new epic but the part of "linke issue to" is not working properly:

When: issue transitioned

Closed

Issue Type equals

Epic

And: Issue matches JQL

component = lost

Then: Create a new

Epic

Same project

And: Link issue to

Trigger issue

Anyone can help me how to figure it out?

Accepted answers

Julieta Dienstmann

Hi @Mark Segall !
I've turned the "Linked issue" field visible in the "CREATE screen" and then tested again. It worked properly then. Thank you so much for helping me to develop this automation.

All comments

Mark Segall

Hi @Julieta Dienstmann - The "And link issue to trigger issue" may be the problem. Am I correct that you've added a separate action after the create issue to link the new Epic to the trigger? If so, this won't work because you're not in the newly created issue at this point and you're essentially telling the trigger issue to link to itself. You have two options:

On the create issue action, you should be able to add the field Linked Issues and link the new Epic to the trigger
After the new issue action, you could add a new branch into "Newly created issues" and add your linked issue action there.

Julieta Dienstmann

Hi Mark, thanks much for your reply.

Yes, you're correct about the assumption that I did a "separate action after the create issue".

Mark, I've tried both options that you've suggested, but it's still now working:

What I'm trying to do is to move an Epic to done status.
If this Epic has a certain value in the field "component", a new Epic will be created. So far, this automation is succeding in doing this.
Then, the automation must relate/link this new epic to the trigger issue (that is also an Epic). This is not working.

I'll add the screenshots of both solutions that you suggested.
Please, can you help me to figure out what's happening?

Is there any other way to link an epic to an epic. I've tried to use "epic link" for this, but it also doesn't work.

Mark Segall

Your first screenshot looks like you configured things correctly. The only thing I can think of as to why it wouldn't work is that the Linked Issues field isn't on the Create screen for your Wave issue type. So, I would check:

The rule's audit log to verify that it shows successful
if the Linked Issues field on the Wave Issue Type CREATE screen

To explain your second approach, the branch relationship type is set to current issue which would be the trigger issue. Instead, it should be All Created Issues.

Julieta Dienstmann

Hi @Mark Segall !
I've turned the "Linked issue" field visible in the "CREATE screen" and then tested again. It worked properly then. Thank you so much for helping me to develop this automation.

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