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!
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.
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?
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....
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
