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 - How to associate an Epic (created in the automation) to an existing Story

Emiliano Visioli_eb2tr1

Hi all,

I need to define an automation that, starting from Story, it creates an Epic and than another issue.

My problem is how to associate the story to the epic as I can only find Link issue action and I don't want a link, I want that story be like created from the Epic.

Is it possible?

Thank you,

Emiliano

Accepted answers

Alex Koxaras -Relational-

Hi @Emiliano Visioli

You don't link Epic to standard issue types like that. You simply edit the standard issue type Epic Link to the Epic's key.

All comments

Alex Koxaras -Relational-

Hi @Emiliano Visioli

You don't link Epic to standard issue types like that. You simply edit the standard issue type Epic Link to the Epic's key.

Emiliano Visioli_eb2tr1

yeah, forgot about this detail

issue solved, thank you!

Emiliano Visioli_eb2tr1

Hi @Alex Koxaras -Relational- in the same Automation I'm trying to copy a field value from the created epic to the trigger story but an error occurs in the editing action as it can't find the epic from where to copy the value.

In attachment:

- The action with error

- The audit results

- The whole automation (that works fine until the last action)

I don't understand it can't be found the value as the epic has been correctly created and associated to the trigger story. I've already checked that the field is included in both issue types.

Thank you,

Emiliano

Ste Wright

Hi @Emiliano Visioli

Just as an additional suggestion, use Parent rather than Epic Link for the parent/child relationship. Parent is replaced Epic Link in the near future and should already be available on your instance.

---

For your second query, you could try putting in a "Re-fetch issue data" action prior to the action to copy data from the Epic.

This "refreshes" the trigger issue to the latest state (i.e with a parent) prior to subsequent actions. I tried with this, and it let me copy field data from the Epic, like you need.

Example rule below, to show a potential order to use:

Trigger: Issue Created
Action: Create Issue
- Issue Type = Epic
Action: Edit Issue - this edits the trigger issue
- Parent = {{createdIssue.key}}
Action: Re-fetch Issue Data
Action: Edit Issue - this edits the trigger issue
- Field = Related PR
  - COPY FROM Epic Issue
Branch: Related Issues
- Type = Most recently created issue - this edits the Epic
  - Branch-Action: Edit Issue

---

Let us know if this works!

Ste

Welcome!

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

Quick Links

Find more posts tagged with

jira

data-center

jira-software-data-center