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

Updating Epic Link via automation

Sean Wiese

I am new to Jira Automation, and working on a scenario where on a transition, I am creating linked tickets. The original ticket is part of an epic, and I would like that epic to also be on the newly created tickets.

Happy to provide additional details.

screenshot is the relevant portion I am stuck on.

Screen Shot 2020-08-17 at 5.36.01 PM.png

Accepted answers

Mark Chaimungkalanont

Hey there Sean,

You should be able to set the Original estimate and the Epic Link in the Create issue action itself without need the extra Edit actions. You need to set the value of the Epic Link to the "Trigger issue"

If editing the Epic Link isn't working, are you using a NextGen project? They deal with Epic Links differently to Classic projects

Cheers,

Mark C

All comments

Mark Chaimungkalanont

Hey there Sean,

If editing the Epic Link isn't working, are you using a NextGen project? They deal with Epic Links differently to Classic projects

Cheers,

Mark C

Ste Wright

Hi @Sean Wiese

Can you provide the full rule?

Mark's method of utilising the "Copy From..." function for setting field values is the ideal option for this issue - but if there is more to the rule it might benefit to see this

Ste

Sean Wiese

Mark - that was def my first choice to set all the things in the create. but I ended up with the edit action since that seemed the only way to get the Orig Est field to work.

added details of the create and the whole trigger.

Not using a next-gen project.

I may just not be groking the "copy from" term, as I dont see that in the epic link options.

also attached.

Screen Shot 2020-08-18 at 8.38.21 AM.png Screen Shot 2020-08-18 at 8.35.55 AM.png Screen Shot 2020-08-18 at 8.37.39 AM.png

Sean Wiese

thanks! updated via reply on Mark's comment.

Sean Wiese

and solved. I guess I just didnt see the field to set as a "copy from" action. seems to be working now, in the create action!

Marc Isikoff_o8qjap

And if we change the scenario slightly to automate creation of an Epic then a Story, how do we establish Epic Link on the story as triggeringIssue is not the Epic nor can we Copy from Epic issue (not established yet) nor Parent Issue (for sub-tasks only)

Marc Isikoff_o8qjap

Nevermind found it: {{#createdIssues}}{{key}}{{/}}

Welcome!

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

Quick Links

Find more posts tagged with

automation