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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

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!

2 comments

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

Hi, 

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

Comment

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

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

5,409 views 22 38
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