Our active sprint is gone

Jörn Seifert_g8w6k8

Working on a free Jira Cloud instance with one productive project und two test projects.
Yesterday I played around in one of the test projects and created a sprint 17 and two boards and more status and so on - in the end I "Completed Sprint 17" there.

Today the sprint 17 in our productive project is gone. No hint that it ever existed. 

The productive stories, tasks and bugs have an entry in field "Sprint", that points to the sprint 17 of the test project!!!

 

How can this be and how can it be repaired?

Could someone have an eye on that

Trudy P Claspill

Hello @Jörn Seifert 

Welcome to the Atlassian community.

There are a few things you need to know about sprints.

1. Jira does not require sprints to have unique names. It assigns unique numeric ID's to them in the database, so it doesn't matter to Jira if you duplicate a sprint name.

2. There is no restriction on which issues can be added to a sprint. If you create Sprint 17 in board A which contains issues for only project XYZ, you are still permitted to go to an issue in project EFG and edit the Sprint field of the issue directly and select Sprint 17.

3. A sprint will display in a board if
a. It was created in that board, or
b. It has an issue in it that is within the scope of the board's filter.

Once an issue from your productive project got added to Sprint 17, then Sprint 17 would be displayed in the productive project's board, and more productive project issues could be added to it.

In this situation you now have two boards sharing one sprint. Since the sprint was actually the same sprint in both boards, completing it in one also completed it in the other.

To repair this you would need to reopen Sprint 17, and also create a new sprint in your board for your productive project. Move all the productive project issues from that reopened Sprint 17 to the new sprint. When you remove that last productive project issue from Sprint 17 it should stop displaying in the productive project board. That assumes that it was truly created in the test project board. Then you can re-complete Sprint 17.

Then proceed with starting and working through the new sprint you created in the productive project board.

To help avoid this in the future make sure that you name your sprints in a way to indicate the project or board where they are being used. That will provide a clue to your users if they try to add an issue to the sprint incorrectly.