The "linked issue" doesn't work in Clone issue

[flourish_x_yang]

• what version of Jira are you using: Cloud, Server, or Data Center
  

  Jira v10.3.8

  alm-jira.systems.uk.hsbc
• images of any relevant trigger / actions / conditions / branches

• explain what is not working as expected and why you believe that to be the case
  I explicitly set the Linked Issues "field" in the Clone action to link the cloned issue as "is supply ticket for" for "trigger issue". But nothing happened.
  The Clone Issue add a cloned link between 2 issues, but it's not what I need.
  The cloned issue is in APICLOUD project, different from the trigger issue which is in SPCOELAB project.

[Bill Sheboy · Accepted solution]

Hi @flourish_x_yang 

What is the scope of your rule: single-project, multiple-projects, or global?

With a single-project scope rule, the Clone Issue action can create issues in other projects, but I believe the linking happens afterwards and so perhaps is impacted by the rule scope.  Thus, you can try two things:

• Change the rule scope to multiple-project and re-test the rule
• If that does not solve this, please try splitting the linking into a separate step:
  • action: clone issue
  • branch: to most recently created issue
    • action: link issue, to the trigger issue

Kind regards,
Bill

[flourish_x_yang]

It's single-project. I achieved it with your second suggestion. Thank you.

But it proves this is a bug for the "Clone Issue" action: the "Linked Issues" function doesn't work.

[Jens Schwendemann]

I actually had the same issue but was working on a manual trigger and the above suggestion using a branch did not work.

It might be missing permissions to switch the scope of the rule to contain multiple projects / spaces or multi space might just not be possible on manual trigger.

Anyways: I figured that the branch was not seeing the newly created (cloned) ticket, no matter using "most recently created work item" or "all created work items" in branch.

What I ended up with was using a variable. I filled it directly after the cloning action and filled it with {{createdIssue.key}}. I then used that variable in the direct next action to actually create the link (from a POV of the trigger issue).

HTH

Jens

[Arkadiusz Wroblewski]

@Jens Schwendemann 

Glad that this or other way you get to solve it.

😊

Best,

Arkadiusz 🤠 ☀️ 

[Arkadiusz Wroblewski]

Hello @flourish_x_yang 

Clone issue is not a true Jira clone. Atlassian explicitly says that this action creates a new issue, the cloned issue is not linked to the original issue, and due to API limitations it does not clone issue links. That is different from the normal Jira UI clone flow, where the original and cloned issues are linked.

You posted a screenshot, but you did not explain what you want to achieve.

Branch automation rules to perform actions on related work items | Cloud automation Cloud | Atlassian Support

This KB should be for sure helpful for you.

[flourish_x_yang]

No, it added a clones link after it created a new issue in another project.

I want to add "is supply ticket for" link on the new issue, by explicitly setting the Linked Issues "field" in the Clone action:  "is supply ticket for" for "trigger issue". But nothing happened.