Inherit all fields to create new clone issues except with 1 or 2 custom field change

[Diana]

I don't know if this is remotely possible unless it's the biggest manually edit I'll ever have to do.

I have 2000+ issues that I basically need to make copies/clones with all of it's custom fields, assignees, linked issues, and tabs filled out exactly the same, except with 3 specific fields that needs to be different.

Example:

Issue Type: Original Bug
Custom Field A
Custom Field B
Custom Field C
Custom Field D 
Custom Field E
etc.

x2000 issues. Create 2000+ new issues.

Issue Type: New Bug
Custom Field A (value is the same as Original Bug)
Custom Field B (has a new value)
Custom Field C (has a new value)
Custom Field D (value is the same as Original Bug)
Custom Field E (value is the same as Original Bug)
etc.

It doesn't help also that this issue type has about 50+ custom fields as well each unique with single select list, multi select list, checkboxes, text fields, etc.

I tried exporting the 2000+ issues as csv, but if I want to import, the ones that were selected as multi option fills a new column rather than using (value 1, value 2) separating. I'm looking for an easier way to pull this off and without having to resort to a plugin. I only have Structure and Scriptrunner.

[Sachin Dhamale · Accepted solution]

@Diana Gorv ,

I am also thinking to export and import an issue i think that is the easy way i can think of.

For multi option field you can make changes in the filed and merge columns in one columns with comma separated values that you can do through some excel formula.

Or

You have script Runner plugin in that we have one post function clone issue and link which you can use. There you can also select which field you want to copy with new issue type.

For this you need to create self transition and use this postfunciton and perform the bulk transaction.

Accept the answer if it helps and let me know if you have any question.

[Diana]

Hi @Sachin Dhamale 

I think I'll do a combination of both. I'll export the issues and customize the custom fields that needed to change (thankfully they are all the same value), then import then to create the new issues. Even though it's a lot of columns on the excel, as long as it's csv, I'll be able to put it back into Jira.

I didn't even think to look at ScriptRunner's Browse built-in scripts! I'm so used to have to make everything customizable that I default look under Listeners and Behaviors. I'll use the Clones an issue and Links script to help me clone the specific links for these issues (turns out the requestor have a list of links that can make this easier).

Thank you! I'll be sure to remember to look under Browse or Built in Scripts before trying to make something customizable.

[Eric R Hartway]

Best I can think of is to create a new transition in your workflow, then add a post script to create a linked issue on transition that copies all the data over, or sets the new data, to the linked issue.

Then, do a bulk "Transition Issues" action using that transition.

I think you can then do another bulk edit to clear the linking if need be.