Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Error when splitting issues



during the split, the Account and Team fields remain empty and the content is not transferred. In our opinion, this is a bug.

The split function is very important for us and my colleagues need this function. Please fix this bug as soon as possible.

Cloning the issues is not a workaround for us.

Is there a workaround for this?
When will the bug be fixed?


Best regards


2 answers

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

0 votes
Trudy Claspill Community Leader Jun 09, 2021

I can see by you comment on the issue that you are already aware there is an open Suggestion in Atlassian's backlog to support copying Custom Field data when using issue splitting.

As per this post, a work around is to use the Automation tool to edit the new issues created by the split and copy the data from the source issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events