Solved:Completed sprints are showing in project backlog. How can I hide them, without deleting them?

[Susann Calvert]

We have a situation in our team-managed project board where suddenly, right after completing a sprint and starting a new one, all previously completed sprints in our project are showing up in the project backlog again, with the historical dates still in there, but somehow seem to be registering as future sprints. We don't want to delete the sprints, as we're not sure what the implications are if we do, and we don't want to lose data or reports. 

Anyone ever experienced something like this who can weigh in, so we can fix it?

[Piyush A (STR)]

Hi, Unsure about the case - but never experienced such.

All the way - it's good to review the changes in the project fields and especially the filter of the board.

Now, check if the old sprint data (story, etc) - do they belong to the new sprint or future sprint any and/or do they belong to the filter too.

If above is unsure, kindly share the Board filter and some ticket details (of old sprint and existing future sprints)

[Susann Calvert]

Project fields have not changed too much - we added maybe one, but it shouldn't affect the completed sprints showing up again - and board filters have not been changed. No modifications were made to the board filters, as far as any of the project or board admins have reported.

Some older stories existed in completed sprints, but got moved to the future sprints if they were not closed. But it makes no sense that these sprints have been now somehow been set to future sprints, which need to be started and completed again, without any adjustments having been made. 

[Piyush A (STR)]

That’s true, they should not be shown

can you share the board config?

try to add more into jql like

'project' = 'Project-1' and sprints not in closedSprints)₹

[Susann Calvert]

Hmmm. Have checked, but it's not in the board where the problem lies. It's in the backlog of the project itself where the issue lies. Unfortunately, I am also not the admin for the whole company. 

I'll reach out to our primary admin again, but for reference, this is what it looks like. In the example, all 3 of those sprints were completed last year already, but somehow one day, they started showing up as not closed, future sprints.

Maybe someone else in the company updated the configs by accident, and didn't revert them back. 








I'll reply back again once our primary admin gets in touch. 

[Piyush A (STR)]

Here, you can check for board config without an admin

[Susann Calvert]

As I mentioned before, it is not in the board where the problem lies; it is in the backlog. I have checked the board config for our boards anyway - nothing regarding filters can be set from here. 

 

[Susann Calvert]

We figured this one out - our new Copado/Jira/Salesforce sync updated the values of the isCompleted for previous Sprints. 

We simply took the manual work road, and closed them all in that way, making sure to check if they had an previously existing tickets.