You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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!
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?
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.
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 you split an issue if cloning is disabled? If not; is there a workaround for splitting issues?