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?
thank you
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.
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?
Can you split an issue if cloning is disabled? If not; is there a workaround for splitting issues?
Recommended Learning For You
Level up your skills with Atlassian learning
Atlassian DevOps Essentials
Learn to manage the product lifecycle by building, automating, and improving processes with Atlassian's approach to DevOps.
Jira Automation
Reduce project complexity and optimize your team's processes through the power of automation.
Bitbucket Pipelines Configuration
Build better software and release more often by learning how to implement a CI/CD solution with Bitbucket Pipelines.