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

Splitting vs. Cloning

I would like folks' opinions on situations when splitting an issue is better than cloning and vice versa.  What happens to the sprint report and team velocity in each instance?  thanks!


Hi Aimee,

We introduced splitting because cloning was really heavy weight and in planning meetings we often wanted to break stories into smaller pieces.   Under the hood splitting does an issue clone but it changes the summary and estimates to what you provide instead of what was in the original issue.

For the reports the cloned issue will have to same estimates (time spent, story points, whatever you're using) as the original issue.  Split issues will have the new estimates you put in.  Both split issues and cloned issues should show up in the same sprints and epics as the original issue.

Like # people like this

i like the concept of splitting vs. cloning but how do we ensure all the attachments and notes move with it? by checking 'include sprint values' or is that not an option.

my question on velocity is, if you split the issue and then mark the original issue as done, then the team will have those points in their velocity right?

thank you

Like Debrenee Fisher likes this

When you split an issue the attachments and notes (we call them comments) don't get copied to the new issue. 

When you clone an issue you can check "Clone attachments" to move the attachments to the new issue, but there's no way to copy comments.


For velocity: Yep, when the original issue is marked as done the team will get those points included.

@Matt Robertson And there are plans to fix this and carry over the important comments?

Hi @Eric Raymond,

We don't have any plans to make changes to this feature.

This is sad.  There's so many parts of Jira that fail to cover common use cases  or work from one screen and are absent in another.  I know I'm venting in vain....


Can we split the issues that are from previous sprints or current sprints?

Like christine_stpierre likes this

Apparently only from the backlog, not in the sprint board


Log in or Sign up to comment
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,113 views 34 44
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you