Exclude fields from being copied when clonning an issue using groovy script

[Oded Priva]

Hi,

I'm using script runner 'Clones an issue and links' to clone an issue.

How can I exclude cusotme fields and non custome fields from being cloned?

What is the syntax to use in the "Additional issue actions" box?

Thanks.

[Paresh Gandhi]

if field is custom

import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.ComponentManager
ComponentManager componentManager = ComponentManager.getInstance()
CustomFieldManager customFieldManager = componentManager.getCustomFieldManager()
def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'CustomFieldName'}
issue.setCustomFieldValue(cf, null)

[JamieA]

You need to just null out the fields you don't want to copy, eg

issue.assignee = null

etc

[Kate McAnespie]

It seems Sprint cannot be nulled out?

[JamieA]

I would think it can... What code did you use?

[Matt Shelton]

Jamie, did you ever determine if this was actually possible?

[Kate McAnespie]

def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'Sprint'}
issue.setCustomFieldValue(cf, null);

[JamieA]

Yes... just zero out any field you don't want copied.

[Matt Shelton]

Thanks Kate - I ended up doing exactly that.

[עדי וקנין]

Hi,

I also tried to apply this on the scriptrunner listener but it doesn't work. 

I copied kate lines to "Clones an issue, and links" additional. can you please explain how you did it?

[Kate McAnespie]

Did you Define the Custom field manager first?

import com.atlassian.jira.component.ComponentAccessor

def customFieldManager = ComponentAccessor.getCustomFieldManager()

def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'Sprint'}
issue.setCustomFieldValue(cf, null);

[עדי וקנין]

What am i doing wrong?

[עדי וקנין]

Kate, can you help me please?

[Tim Yuan]

i got same setting with your screen shot. 

Did u fix this issue? 

[Bob Swift]

Clone Plus Plugin for JIRA provides options for customizing clone operations including field excludes. This provides issue actions (not workflow functions) that can help with some team work flows that don't need to be associated with a issue transition.

Create on Transition Plugin for JIRA does provide workflow functions for creating issues and subtasks with control over which fields get copied to the new issue. Not exactly cloning but with most of the same capability.

[Nic Brough -Adaptavist-]

The clone in groovy effectively calls most of the internal Jira clone function, which really does just copy everything.

To clone an issue with fields being dropped, you'll need to write your own script that can pull data from an existing issue and use bits of it to create a new issue.

[JamieA]

I'm not sure this is the case, not as I remember it anyway.

[Suresh Bhandiwad]

Hi @Nic Brough -Adaptavist-,

Can you please help with the script for Jira cloud in postfunction or listener? The script in community more intended for Jira server.

I have two custom field which I want to exclude from being copied when cloned an issue in Jira cloud. 

Thanks,
Suresh

[Nic Brough -Adaptavist-]

This is a comment on a 5 year old question, so everything is out of date.  Please ask a new question and describe your exact environment and what you want a script to do,

[Suresh Bhandiwad]

Sure Nic. Thanks!
https://community.atlassian.com/t5/Jira-questions/Exclude-or-clear-custom-field-for-a-cloned-issue/qaq-p/1179262#M375185