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:
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
This KB should be for sure helpful for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.