nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Groovy Script to Clone an Issue and it's Linked Issues (all fields)

Katrina Thacker_y4q6st

Hello! I'm trying to use the JMWE "Create/Clone Issues Post Function" capability to clone an issue on a transition AS WELL as clone it's linked issues - all fields including custom fields. Essentially I want to create nearly an exact duplicate of an issue and it's linked issues. I'm using the JMWE so I can iterate and create multiples given certain criteria. Anyone done this before and willing to share how? I've successfully used this function to clone the 'parent' issue but struggling how to clone the linked issues and ensure they are linked to the clone of the "parent" issue.

Other info: Jira Server v8.5.3

Scriptrunner: 5.6.14.1-p5

JMWE: 6.2.4

Thanks in advance for your help!

Accepted answers

All comments

Radhika Vijji _Innovalog_

Hi Katrina,

Let's assume on the trigger of the transition "Clone now" you want to clone a parent and issues linked to it through "is related to" link type.

Clone Parent : Add the Create issue post-function to the "Clone now" transition.

Select the destination project from Project
Select the Issue type same as the current parent
Select the link type as "clones"
Using the "Set fields of the new section" set the fields on the new parent (copy or set with new values)
Save the post-function.

Clone linked issues: Add a "Transition Linked Issues" post-function configured as:

Select the Link type as "is cloned by"
Input the transition name as "Clone linked issues" (will be created in the next step)
Add a Delayed execution of 3 seconds
Save the post-function.
Publish the workflow.

Create "Clone linked issues" transition

On the Parent workflow of the destination project (on the same workflow if both parents share the same workflow), create a transition named "Clone linked issues" on the Create transition to the same initial status.
Hide that transition from users by adding a "Hide Transition" Condition

Clone linked issues: Add the Create issue post-function to the "Clone linked issues" transition

Select the Project as "Same as current issue"
Select the Issue Type as Calculated, with value
{{it.fields.issuetype.id}}
Select the Link to new issue as "is related to"
Input the Summary as:
{{it.fields.summary}}
Select "Multiple issue creation" option
In the iterator write the following script:
{{issue | linkedIssues(<span> </span>"clones" ) | first | linkedIssues(<span> </span>"is related to" ) | dump}}
(note that "clones" here is the name of the reverse direction of the "is cloned by" link type used above.
Save the post-function.
Publish the workflow

Now when you trigger the transition "Clone now" the parent and its linked issues are cloned to the new project. Hope this helps.

Regards,

Radhika

Katrina Thacker_y4q6st

Thank you so much Radhika...gonna try and set this up now. Will let you know how it goes.

Katrina Thacker_y4q6st

@Radhika Vijji _Innovalog_ your suggestion helped me overcome cloning the linked issues although I'm having issues with specific fields not cloning as expected; I'm working through that. The bigger issue is that the cloned linked issues are not linking to the cloned issue (they are linking to the original issue). Let me see if I can describe what I'm trying to achieve more clearly:

Project: the cloning is within the same project and all issue types I'm trying to clone are using the same workflow

Scenario: I create issue type = Feature and it has 2 linked issues of issue type Test (will call them Test A & Test ; link from Feature to Test is "tested by"; link from Test to Feature is "tests"

When I transition the Feature to "Ready for Development" I need the following issues to be created:

a) Issue Type "Story" - Clone of Feature with a Platform field = app1 and exact clones of Test A and Test B linked to Story 1 with "tests' link

b) Issue Type "Story" - Clone of Feature with a Platform field = app2 and exact clones of Test A and Test B linked to this Story with "tests' link

I hope that helps and thanks again for all your help!

Radhika Vijji _Innovalog_

Hi Katrina,

My bad. I have provided you the answer for Jira Cloud and not Jira server. Here is what you need to do. Please try and let me know:

Clone Feature: Add the Create issue post-function to the "Ready for Development" transition.

Select the destination project as Same as current issue
Select the Issue type as "Story"
Select the link type as "clones"
Under the "Set fields of the new section"
1. Select the Platform field.
2. Select "Set field value to constant or Groovy template"
3. Input the value
4. ```
it
```
Select the "Multiple Issue Creation" checkbox.
1. In the iterator, input the following code"
2. ```
["app1","app2"]
```
Save the post-function.

Clone linked issues: Add a "Transition Linked Issues" post-function configured as:

On the "Ready for Development" transition add a "Transition related issues" post-function.
Input the transition name as "Clone linked issues" (will be created in the next step) and click on "Add"
Select the "Issue linked to the current issue through the following link type" under "Which issues"
Select "is cloned by" under "Issue Link"
Save the post-function.

Create "Clone linked issues" transition

On the "Create" transition of the workflow create a transition named "Clone linked issues" to the same initial status.
Hide that transition from users by adding a "Hide Transition" Condition

Clone linked issues: Add the "Create issue" post-function to the "Clone linked issues" transition

Select the Project as "Same as current issue"
Select the Issue Type as Calculated, with value
```
it.issuetype.id
```
Select the Link to new issue as "tests"
Input the Summary as:
```
it.summary
```
Select "Multiple issue creation" option
In the iterator write the following script. Note that "clones" here is the name of the reverse direction of the "is cloned by" link type used above.

issue.getLinkedIssues("clones").first().getLinkedIssues("tested by")

Save the post-function.
Publish the workflow

Now when you trigger the transition "Ready For Development" two cloned Stories will be created for the feature with two linked issues each with the link type as "tests" (from test to Story)

Hope this helps,

Regards,

Radhika

Prashant Mali_gaqcq5

Is this solution works for any one.

I have same requirement.

We have parent child issues between two projects. I want to clone complete structure of Parent- Child issues.

Kindly suggest

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server