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; } } }

When splitting a Jira issue, is there a way to copy the custom fields?

Dave Menconi_dmwhx0

According to this document, 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).

Accepted answers

Angélica Luz

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

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

Regards,
Angélica

All comments

Angélica Luz

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

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

Regards,
Angélica

C W_2xjg1h

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

Michael Gloeckner

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.

Best regards

Michael

C W_2xjg1h

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!

IT Platforms_hni4n3

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>"
}
}

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

cloud

jira-software

jira-mobile-apps