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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,553,320
Community Members
 
Community Events
184
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!

3 comments

Matt Robertson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 28, 2018 • edited

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
Matt Robertson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 02, 2018 • edited

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?

Matt Robertson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 02, 2019 • edited

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....

Like Rob J likes this

Hi, 

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

Can you split an issue if cloning is disabled?  If not; is there a workaround for splitting issues?

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events