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?
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.
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 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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events