Closing a sprint & cloning the issue to the next sprint

[Mirmelshtein_ Roi]

Hi All

Our current workflow in Jira is once we end a sprint, it will prompt the user either to move the unresolved issues to the next sprint or to the backlog.

What I want to do is to change that behaviour...meaning I'd like to close the sprint, keep the unresolved issues (not move them) but clone them to the next sprint

Does anyone know how to to this?

[Trudy Claspill · Accepted solution]

Hello @Mirmelshtein_ Roi 

You can't change the built in Complete Sprint process to clone rather than move issues.

What problem are you trying to solve by cloning the issues?

What is actually happening is that the issue retain the record that they were in the sprint you are Completing, and then get the new sprint ID added to their Sprint field. The Sprint field will retain all the Sprint IDs for sprints to which the issue was added and never removed. "Moving" the issue to the backlog or another sprint when you Complete a sprint does not remove that issue from the Completed sprint.

[Mirmelshtein_ Roi]

Hi @Trudy Claspill 

Well what I want to get is the % of done for a completed sprint.

meaning how many issues were done in a sprint out if the whole sprint issues excluding bugs (plan vs actual). I see no option to get this if the issue keeps moving from sprint to sprint and retaining the sprint ID....the only way to see this is via the sprint report but that means calculating it manually....

Can you think of another way to do this?

[Trudy Claspill]

Going forward you could use an Automation Rule to get the information emailed to you when the sprint is completed.

On what would you be basing the percentage? The count of issues? The Story Points in the issues?

Do you have subtasks also? If so, would you expect information from those to be included in the percentage?

Jira does not provide many native reporting options that can be used with sprints that have already been completed. You would have to look for a third party app to help you with that, if needed.

[Mirmelshtein_ Roi]

Precentage is based on the issue count and yes we do use sub-tasks as part of the calculation. How can I create such an automation? 

[Trudy Claspill]

I just noticed that you tagged your post as being for Jira Server. Are you using Jira Server of Jira Data Center?

I'm actually not sure this can be accomplished with automation on Jira Server/DC. I was thinking of how this would be done on Jira Cloud. Some of the necessary functions are not available in Jira Server/DC, such as the Lookup Issues action and the Create Variable action.

I don't have a Jira Server/DC instance where I could actually work on developing and testing the automation.

Start with the Sprint Completed trigger and specify the board when the sprints are managed.

Because the Lookup Issues action isn't available you would then use a Send Web Request action to call the Jira REST API retrieve the issues assigned to that sprint. You may want to use multiple Send Web Request actions to retrieve the issues in groups:

- all the issues in the sprint

- only the issues that are in the Statuses mapped to the right-most column.

The next step I would've suggested was parsing the returned information to get the count of issue returned and assign that to a variable within the Automation Rule, but the Create Variable action is not available in Jira Server/DC.

And then one would use math functions to calculate the percentage.

And then finally sending the result to yourself with a Send Email action.

Given that some of the requisite actions are not available you might want to instead consider looking for a third party app that would help you get the information you want.

[Mirmelshtein_ Roi]

Hi @Trudy Claspill 

Tanks for the detailed explanation !

I'll give it a try although it is seems really over complicated just o create this plan vs actual view