If an agile team clones an issue in JIRA, how does this impact the results of report of Control Chart and Cumulative Flow diagram? Let´s say a team have an origin issue, and does not complete all subtasks during a sprint. They agree they will clone the origin issue, and create a new clone-issue that inherit almost all info. The origin issue is put to done (incl. done sub-tasks) and released, and they continue to work with the remaining clone-issue with sub-tasks in next sprint.
To me the better way of doing it is to just close the sprint, but not the issue. All issues that aren't closed (and all sub-tasks that aren't closed) will be moved either to the backlog (or the next sprint if you want). This is the correct Scrum way of doing it, and Jira allows that.
Essentially, it goes back to the Definition of Done and creating value. An issue with half of it's sub-tasks complete is not complete and adds no value. Scrum also says you only "claim" the story points when all the work is "done"
That's really up to each individual / company. We use it to make a copy of an issue - each sprint we do some maintenance work, so we have an issue with a number of sub-tasks; cloning the issue gives us a copy (with all it's sub-tasks) to use in the next sprint.
I hope that helps to make it clearer
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs