JSM Automation: Set cloned issue to an exiting Epic in new board

[Michael de Marigny]

Hi ... Apologies if this has been asked already and if so please direct me to the post.

We are ruuning JSM as a portal for our users to log issues.  Based on certain rules, there is an automation which clones the issue to different Jira Software boards.  The cloning and interaction works except the assinging of the clone clone to an existing EPIC in the destication board.

Workflow should be:

Issue created in JSM Portal => JSM automation creates clone in JS Board => automation assing the child issue on destination board to BAU Epic.

Thank you in advance for your time and help.

[Ste Wright]

Hi @Michael de Marigny 

You've got a branch after the clone action - which is for "all linked issue types" - is this meant to locate the cloned issue, given that's where the parent is being added?

If yes, I would change the branch to "Most recently created issue" - this will reference the issue created during the clone action.

Also ensure this is a multi-Project or Global rule (created via Settings > System > Global automation). This allows you to set values across all in scope Projects.

---

However, I'm unsure how the Epic is located based on the current setting of the edit issue action, with Parent being assigned the value "Current issue".

How is the Epic being located?

If it's a single Epic (i.e called "BAU Tasks") - you could just set it to that specific issue key?

---

If you could provide more details about the wider rule, that might be beneficial :)

Ste

[Michael de Marigny]

Hi @Ste Wright 

Thank you for helping out.

I have made the change to the clone action from "all linked types" to "Most recently created issue".  

I can confirm that all boards involved are comany based projects and it is a global automation rule.

The EPIC exists on the board where the cloned issue is created.  The EPIC is called BAU Tasks and is designed to add any child issue created as a result of an incident.  So the goal is to clone the issue that was created by the JSM portal in the new board and assign it to an existing epic.

Hope that helps

[Ste Wright]

Hi @Michael de Marigny 

You should be able to set the Parent to that Epic's specific Key in the rule, which should simplify things!

Let us know if this all fits together for you!

Ste

[John Funk]

Hi Michael - Welcome to the Atlassian Community!

How are you linking the two issues together? Because all I see is that you cloned it. Are you assuming that the clone action will create a link? Have you verified that?

[Michael de Marigny]

Thank you John.

Once I have created the clone, I'd like to assing the issue to an existing Epic called BAU Tasks in the new second project board.  Its a stock standard EPIC that we assign day to day issues.

[John Funk]

Understood, but you didn't answer my question. How are the two issues currently getting linked and when? 

[Joseph Chung Yin]

@Michael de Marigny -

Welcome to the community.  You should add an action to "Re-fetch issue data" after the cloned issue is created in your Jira Software Application project.  Afterward, conduct your issue operation (i.e. edit the issue to update the Epic Link to your existing Epic).

In your existing rule, what is the error that you are encountering?  Can you try to use "Log action" to see the problem in the rule's audit log?

See the following reference link on how to troubleshoot your automation rule - https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.