When I use the "Clones an issue and links", I am able to create 19 different Cloned issues in different projects, using 19 different post function in the same workflow action, but am having a problem where the Cloned issues shows all of the links to the other Cloned issues, so it is hard to pick out the Original issue. What we are looking for is:
(a) When viewing the Original - see all of the Cloned issues linked
(b) When viewing a Cloned issue, only see the Link to the Original issue.
Is there a way to use script in the "Additional issue actions" to stop the Cloned issues from being linked to each other?
Background.....
Our current implementation for tracking Security Vulnerabilities in multiple products is using Parent and Sub-tasks, where multiple Sub-tasks are created in a JIRA Post Function script. The different teams will investigate and work through to resolution on their individual product's Sub-task. The problem with the Parent/Sub-task is individual product teams cannot associate their Sub-task to their team's Sprint, (Sub-task inherit Sprint from Parent) so we need to move this same capability from Sub-tasks to another Issue Type and use a unique Issue Linking to identify.
From the Parent we can see the all of the Sub-tasks, while from the Sub-tasks there are no associations to the others created at the same time.
When using the "Clones an issue and links"the viewing of a Cloned issue is causing concerns as this put the Activity further down the page, but more importantly, the association of the Outward and Inward links are lost when multiple issues are cloned during the same workflow action. Was hoping there is a way to limit what Links are created.
