How to remove old closed sprint from current sprint issue ?

[Parveen Vats]

Hi Team!

When sprint closes, we roll over remaining issues to next sprint. Now this becomes my current sprint, but it shows the old/closed sprint also attached to the issue. 
How to remove it from the issue ? Can we bulk remove as well ? 

Refer attached image : Need to remove Sprint 14 but unable to do so.

Kindly assist.

Regards

Parveen

[Trudy Claspill · Accepted solution]

If you remove the previous sprints, in which an issue was not completed, that is going to affect the Sprint Reports and Velocity Charts for those previous sprints.

What problem are you trying to solve by removing those sprints?

[Parveen Vats]

Hi @Trudy Claspill 

My Sprint 14 was of 2 weeks ::  22nd may to 2nd June

I have created one filter query in advance search only : project = WW AND status = Released AND Sprint = 49 ORDER BY status DESC, cf[10020] DESC, reporter DESC


>>which extracted 118 results as it is showing tickets released before Sprint 14 as well
>.actual number of tickets released in Sprint 14 is less 

Q1: Why there is a difference?
Q2: Want these issues to show up in better presentation format {or Board format}. That's why trying to create a Board but now got to know that Board shows up for Active Sprints, not closed ones.

If you can help, please

Regards

Parveen

[Trudy Claspill]

Your filter applies to the current status of issues. It will get you all issues from the WW project that currently have a status of Released and were assigned to the specified sprint. It is not constructed to provide you the list of issues released during the sprint.

If you use the Released status value to indicate an issue was released, and you want to know the issues that were set to that status during a specific time frame, then the JQL you need is:

project = WW and status = Released and status CHANGED TO Released DURING("<insert start date of sprint>", "<insert end date of sprint>")

[Parveen Vats]

Hi @Trudy Claspill 

JQL suggested by you to resolve my current problem works out perfectly well. Now, representing this data on Pie chart gives good and accurate visuals as well.

Thanks a ton !!

Regards

Parveen

[Nic Brough -Adaptavist-]

It's not a bug - destroying the information that a team attempted to deal with a story during a sprint is not what we should be doing with an issue tracker.

[Parveen Vats]

Why @Nic Brough -Adaptavist-  ?

History cannot be deleted of any ticket. It would remain.

But, if issues are getting done in Current Sprint, then it should not affect the previous Sprint reports or queries by showing up there as well etc 

Here, I am just trying to understand the rationale behind things, as I am a learner and exploring and learning things.
I am surely not a Pro like you.

Hope you understand.

Thanks

[Nic Brough -Adaptavist-]

The rationale is simple - don't lie.

This issue was part of a sprint, don't try to pretend it was not.

The current sprint is a different thing.

[Parveen Vats]

Dear @Nic Brough -Adaptavist- 

Nowhere I am pretending that this issue was not a part of Sprint

I am sorry, you are getting everything wrong here.

I am not interested in any arguments here.
Thanks but No Thanks for commenting like this.

Difficult to digest that you are Community Leader

Cheers!

[Manoj Gangwar]

Hi @Parveen Vats ,

The behavior you are describing with Bulk operations no longer clearing the sprint field is a Bug we are tracking here:

• https://jira.atlassian.com/browse/JSWCLOUD-17215

Make sure to add yourself as a watcher if you would like to receive updates on the bugs status.

Currently removing an issue from a sprint requires reopening the closed spring and moving the issue from the active sprint to the backlog then re-closing the sprint, details on reopening a closed sprint can be seen here:

• https://confluence.atlassian.com/jirasoftwarecloud/reopening-a-sprint-785332001.html

[Parveen Vats]

Hi ! @Manoj Gangwar 

At present, I think re-opening of Sprint. moving tickets to bklog and then closing sprint should not be the right way.
Maybe, thisss might be the only way - haha
I'll continue exploring and learning.

Anyways, thank you so much for the response.