Automation - How to associate an Epic (created in the automation) to an existing Story

Emiliano Visioli March 15, 2024

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

1 answer

1 accepted

2 votes
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 15, 2024

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 March 15, 2024

yeah, forgot about this detail :)

issue solved, thank you!

Emiliano Visioli March 15, 2024

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,

EmilianoBrokenRule.pngaudit.pngautomation.png

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 16, 2024

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

Like Emiliano Visioli likes this
Emiliano Visioli March 18, 2024

Hi Stephen,

I confirm that using re-fetch action now the rule works! Thank you!

In my instance I can't see Parent field, I tried to use it but it returns error so for the moment I still use Epic Link.

Thank you again,

Emiliano

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 18, 2024

Glad it works!

And ah, it's Data Center - apologies, yes it's still Epic Link.

Ste

Suggest an answer

Log in or Sign up to answer