How to remove a single sprint from tasks in bulk?

[Theresa Rogers]

I keep having an issue where resolved issues roll forward to the next sprint which is now causing hundreds of tasks that are already resolved to show in the current sprint.  I have looked for resolutions to this issue but only found solutions that will remove ALL the sprint values from these tasks.  I want to retain those historical sprint values (we did work on the tasks in those sprints).  However, how do I remove the current sprint from these tasks without removing all the other sprint values in the field?  Thank you!

[Radek Dostál]

From what I remember an issue can only be actively part of a single sprint at a time, whatever sprint they were in before is more of a "historical" thing but not an actual field value of 'Sprint' itself - if I am not mistaken here. Can you provide a link to some of those solutiuon/articles you mention? Would like to check that.

I am under the impression that removing the sprint value will just remove the current sprint, but not remove any historical references (however didn't test so could be wrong).

Other than that if you keep on getting resolved issues rolling forward to the next Sprint, chances are that:

 - on your Scrum board, those issues were not in the right-most column -- this is what during Sprint closure the board will look at

 - and/or, you do not provide 'Resolution' value to your issues, when they're in the resolved status; Jira does not "care" about the status, it cares about the 'resolution' field to determine if an issue is resolved or not

Is any of the 2 above the case?

[Theresa Rogers]

I found these: https://community.atlassian.com/t5/Jira-Software-questions/Stories-in-alternate-quot-Done-quot-categories-are-not-properly/qaq-p/1432995 

https://community.atlassian.com/t5/Jira-Software-questions/Issues-marked-as-Done-still-appears-in-a-New-Sprint/qaq-p/732831

https://community.atlassian.com/t5/Jira-Software-questions/resolved-subtasks-are-still-being-rolled-to-the-next-sprint/qaq-p/1448533

https://community.atlassian.com/t5/Jira-questions/Closed-issues-are-being-rolled-over-every-sprint/qaq-p/1157862

I have already closed all the other posts I looked at.  But they all said the same thing about tasks workflow statuses maybe not being mapped correctly to DONE or showing as resolved.  I just verified my workflow statuses are mapped to DONE and also in the right column on my board. 

They mentioned to look and see if subtasks were open - that would explain why parent tasks rolled forward.  I checked that too and that is not the cause.  We only have a handful of subtasks in the last few years yet nearly 500 resolved tasks continue to roll forward.

They all also mention to process bulk changes and simply leave the sprint blank to fix this.  I just tested this on two tasks and it wipes out all the sprint values, not just the current/new sprint I just opened this week.  I have to be missing something in our setup...  I'll see if I can go through and capture screenshots of what I'm seeing and add them here.

[Theresa Rogers]

It looks like some of my statuses don't cause Resolution = Resolved.  For example status "Cancelled" causes Resolution "Archive."  This is one of the tasks that continues to roll forward.  Any insight on where I go to update this?  When I look in the Workflow and click on Cancelled it is set to Done.  Is there another page where to set Resolution?

[Daniel Ebers]

"Archive" as a resolution is a valid value by means how Jira works.
This should not be the cause from my opinion.

If you have, for example, Script Runner (App) there is the possibility to do a bulk fix of resolutions while, to be honest, I do not believe it is necessary in this scenario.

If your question was on where to change behaviour so the resolution is something else than "Cancelled" you would have to edit the workflow for the transition which puts the resolution to the issues (most likely one of the last transitioning to something like "resolved" / "closed").

[Theresa Rogers]

I don't believe I have script runner - if I did I doubt I'd be able to write a script easily to do this myself.  I think my issue is two-fold.  1) Some statuses might not be marked as resolved and that is why they continue to roll forward to the next sprint and the next.  2) Now that I have a ton of resolved tasks in my sprint, I want to get them out of this sprint in bulk.  However when I try a bulk change and change the sprint field to ' ' it removes all sprint values that were ever in that field, not just the current sprint.    If there was simply a way to remove the current sprint only from a batch of tasks, that would solve the immediate issue.

[Daniel Ebers]

The right-most column in a board will classify issues as "done". Cancelled on the other hand counts as a valid resolution per definition.
If the resolution is missing you could fix it through a bulk edit. In case you would do it via Script Runner there would be needed no code - this is a built-in script (however, this can be neglected as you say you don't have the App).
The information about the sprints the issue was in should be kept in order being able to do historical reports.