Add issues to closed sprint?

Hi,

We recently closed a sprint in Jira, and started a new one. However there was one issue that belongs to our current sprint, but really should belong to the closed sprint. The issue is resolved, and deployed into production. So by all logic, it really belonged to the old sprint. And now I just want to move it into that sprint. But I can't do that, since the sprint is marked as done. And I can't reopen it, since we already have started on the next sprint, and we don't want to stir things up to much with that sprint.

Is there really no way to manually move a resolved issue to a resolved/done/closed sprint?

5 answers

1 accepted

Hi Jimi,

You can add the Sprint field to the edit issue screen associated to the project that issue belongs to. Then, you can edit the Sprint field and add the SprintID of the correct sprint. To retrieve the SprintID please refer to:

How can I find out the Sprint ID of a particular Sprint

Hope this helps!

Cheers,

Clarissa.

Hi Clarissa,

Thanks, that worked great!

Just one minor thing. In the sprint report for the closed sprint, this issue still shows up under "Issues Removed From Sprint" (it was included in the sprint in the beginning, then removed, and then we forgot to move it back in), instead of under "Completed Issues" as expected. I don't suppose there is a way to re-generate this report?

/Jimi

Renjith Pillai Community Champion Apr 08, 2013

The manual editing of the Sprint is something not expected to be done in GreenHopper and what Clarissa suggested was just a workaround. May be the right way is to just leave it and close in the next sprint as, sprints are timeboxed. Just an opinion

Thanks for your input Renjith. Although my view on this is that computer systems should be adapted to human behaivor, not the other way around. :)


Hi Clarissa,

As Jimi I have a problem with the Reporting tab in the Agile view.

I've forgot to add a task before closing the sprint, I've created a new task and assigned the sprint number (enabled the field in 'editing' task) but it doesn't show at all in the reporting tab, not even in 'Issues Not Completed'

Using v. 6.1.6

Bogdan

I closed a sprint with an issue getting moved on, it gets marked with completd sprint. We then relaised it was a "spike" (custoem issue type) rather than a story and closed it. But the problem is the reporting tab shows it as a not completed story, it's unfortunate the reporting tab is not editable in any way....

Using JIRA Agile v6.1.1

Hi everyone,

I was able to move an issue from an active sprint to a closed one (e.g. sprint 3 to 2). However one unanticipated problem we encountered was that the closed issue did not contribute to the velocity count for the closed sprint. Is this fixable?

Hi all,

I see this original question was back in 2013.  I'm guessing something changed around what values are shown in the Sprint drop-down since I'm not able to associate a ticket with a sprint that has been closed.  If I try to manually type in the old sprint, Jira warns me that it doesn't exist and that it will be added to the backlog, which is not where I want it.  Any ideas?  Is there a way to override this?

I'm in the same boat as Marci - would love to know the current way to do this!

Yeah it looks like you can't use the Sprint ID in the edit screen anymore. 

You should be able to update the sprint with a bulk-change though. It will need the Sprint ID (instructions in the accepted answer above) instead of sprint name.

Hi Clarissa,

As Jimi I have a problem with the Reporting tab in the Agile view.

I've forgot to add a task before closing the sprint, I've created a new task and assigned the sprint number (enabled the field in 'editing' task) but it doesn't show at all in the reporting tab, not even in 'Issues Not Completed'

Using v. 6.1.6

Bogdan

We're considering making the Sprint field editable as suggested here. Are there any downsides to this? Unanticipated bugs, etc.? For example, does moving the field in the UI update other fields that don't get updated when the Sprint field is edited directly?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,305 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot