How does cloned issues in JIRA affects the reports for project?

[Johanna_Torstensson]

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.

1. How will this impact the outcome of the cumulative flow diagram and control chart? e.g. will the done origin issue be credited in the reports?
2. Is there another way to work with not completed issues according to scrum in JIRA? 

[Warren]

Hi Johanna

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"

[Johanna_Torstensson]

Thanks for the reply. When is the clone-feature in JIRA to be used? 

[Warren]

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

Warren

[Johanna_Torstensson]

It does, thanks for your input! :-)