When splitting a Jira issue, is there a way to copy the custom fields?
Asked by Dave Menconi:

According to this [document](https://confluence.atlassian.com/jirasoftwareserver079/creating-issues-and-sub-tasks-950291239.html#Creatingissuesandsub-tasks-Splittinganissue), when you split an issue it doesn't copy custom fields.

But I have a required custom field (platform) that I want to make sure it copied. Otherwise every issue in the system has a platform value except issues created with a split. No bueno!

I'm not sure exactly how an issue split works but, presumably, it has to create a new issue so it has to go through the create issue transition? Is there some way I could add something to that?   

I'm in Cloud using (obviously) jira software in an agile board (in this case Scrum).


Answers:
author: Ang?lica Luz
body: Hello Dave,

Thank you for reaching out to Atlassian Community!

When splitting an issue, it's not possible to copy custom fields on Jira Server or Cloud.

There is a feature request suggesting the implementation of this ability:

* [Save the custom field details when using Split issue feature in Backlog](https://jira.atlassian.com/browse/JRACLOUD-64934)

Please, click on vote and watch to receive updates about the feature.

The documentation you mentioned is related to Server and the Cloud documentation has more details about what happens when an issue is split:
> - The new issue will be of the same issue type as the original issue. For example, if you split a story into two or more issues, the new issues will also be stories.  
> - The new issue will have most of the same details stored in the original issue, including priority, component, label, etc.   
> - The issue details that won't be copied over include work log, comments, issue history, issue links, etc --- though the original issue will be linked to the new issue.  
> - The new issue will have the summary that you entered upon splitting the issue.  
> - If the original issue has estimates, you'll be able to enter estimates for the new issues as well. You can also update the estimate of the original issue as necessary.  
> - The issue status also returns to the first step of the corresponding workflow, and the resolutions are cleared.

[Create an issue and a sub-task](https://support.atlassian.com/jira-software-cloud/docs/create-an-issue-and-a-sub-task/)

Regards,  
Ang?lica


author: C W
body: Hey Dave!

I had a similar use case and was able to figure this out today with the automation tool. Here's how I got it to work:

1. Use the **Issue Linked** trigger pick the **Issue split** type

2. Create a branch rule with the **Destination issue** type

3. Add the **Edit issue** action, select the 'Copy from...' option and click on the default 'Current Issue' value and change to 'Trigger Issue'

Best of luck!

Caurie

comments: author: Michael Gloeckner
body: Hi Caurie,

thank you very much! With the automation tool, the values are taken over when splitting. Very good. That is exactly what we needed.

![https://community.atlassian.com/t5/image/serverpage/image-id/130676iAD16C808AC0C4B2D/image-size/large?v=1.0&px=999](https://community.atlassian.com/t5/image/serverpage/image-id/130676iAD16C808AC0C4B2D/image-size/large?v=1.0&px=999 "Screenshot 2021-02-16 at 15.23.30.png")

Best regards

Michael


author: C W
body: Awesome! I didn't even realize you could change the from to the 'Trigger Issue' so that cleans up my automation and eliminates the 'Create Variable' component. I updated the above steps to match the streamlined process.

Thanks!


author: IT Platforms
body: Any thoughts on how to deal with fields such as the "Team" field that comes from Tempo Planner app which is not an "available" field to be selected in the "choose fields to set" step of edit issue?

I can hardcode a team number into "additional fields" JSON section, but we would need to somehow make that JSON reference dynamic and simply a copy of the parent issue team number:

{  
"fields": {  
"customfield_11001": "**\<team number\>**"  
}  
}


author: Mathias Richter
body: Hi IT Platforms, you can copy the Team field by using this snipped:  

{  
"fields": {  
"customfield_10100" : "{{triggerIssue.fields.customfield_10100}}"  
}  
}

This is what we use for the Advanced Roadmap Team Field. For sure your Custom Field ID will be different, so this needs to be adjusted before you can run the automation in your environment.


author: Alexa
body: Hi IT Platforms,

I found a way to dynamically pull the Team field into the copied issue: <https://community.atlassian.com/t5/Jira-Software-questions/Teams-option-unable-to-edit-using-automation/qaq-p/2197615#M291300>


Tags: cloud

jira-software