the sprint we were working on has disappeared

[magaly]

"I am facing an issue: on two consecutive occasions, the sprint we were working on has disappeared, and the user stories have appeared in the backlog. We don't understand why this is happening, as no one has apparently deleted it. It could be a tool error. Could you help me investigate what is happening

[magaly]

Can I  have a separate backup for each project in JIRA. So I could easily restore individual projects if needed.

[Mikael Sandberg]

Hi @magaly,

Welcome to Atlassian Community!

If you go to Reports > Sprint Reports do you see the sprints that disappeared  in the dropdown list?

If so that would mean that someone closed your sprint when they closed their sprint. This can happen since sprints are not project or board specific but can be used in any project. So if someone by accident select the wrong sprint on another board this can happen. The only way around this to make sure your use unique names for the sprint and also check the box to only show sprints in the current project if you have to set the sprint in the issue view. 

I always recommend that you assign issues to sprints from the backlog, that way you avoid running into the issue of selecting the wrong sprint.

[magaly]

Thanks for your response. However, I wanted to point out that the sprint doesn't appear in the reports; it seems to have been deleted. As I mentioned earlier, they are visible in the User Stories in the backlog, along with their recorded times. But no one deleted it, or at least there's no evidence of that.

[magaly]

I checked the history of each User Story too, and it shows that it was moved. However, the person in charge insists that she didn't do it.

[Mikael Sandberg]

Well, if the sprint has been deleted then there is not much you can do unless you have a backup of your instance.

[magaly]

Thanks for your response. Can I  have a separate backup for each project in JIRA. So I could easily restore individual projects if needed.

[Mikael Sandberg]

No, the backup option that Atlassian is working on would be for the whole instance, not for separate projects. There are apps in the Marketplace that can do granular recoveries, for example Revyz data manager 

[magaly]

Sorry for continuing to ask: Attached, you will find two images that clearly illustrate the evolution of two incidents. Initially, both were recorded in Sprint 177, but at the same date and time, there is a movement observed that relocates them to another position in the history. Does this discrepancy indicate that Sprint 177 was deleted at that specific moment?

[magaly]

[Mikael Sandberg]

Yes, and no. The history shows that the issues were removed from Sprint 177, but it does not indicate that the sprint was removed. But since you cannot see the sprint when you go to the Sprint report, that indicates that the sprint was deleted.

[Ana Magaly Reyes]

Thank you, could you suggest how to do this? Checking the box to display only the sprints in the current project.

[Mikael Sandberg]

If you are using different project then the check box to only display sprints in the current project would do the trick. But as I mentioned in my first answer, I always recommend that assign issues to sprints from the backlog, that way you are avoiding the situation of adding the issue to the wrong sprint by mistake.