Hi, I encountered a weird problem with mixed up sprints. We manage multiple projects and each project has its own sprints (sprints are named differently ( | Sprint . ) or something similar to that. But they all are never the same. This issue happens again for a second time --the first time it happened was last year but it was too late to fix anything because the sprint had already started. So, we create several sprints per project beforehand (5 or 6 sprints in advance). But there will always be one of the sprints gets mixed up with another project. Following are what correct sprint names are supposed to look like: Project A * Project A | Sprint 1.2025 (active sprint) * Project A | Sprint 2.2025 (future sprint) * Project A | Sprint 3.2025 (future sprint) * Project A | Sprint 4.2025 * Project A | Sprint 5.2025 Project B * Project B | Sprint 2025.1 (active sprint) * Project B | Sprint 2025.2 (future sprint) * Project B | Sprint 2025.3 (future sprint) * Project B | Sprint 2025.4 * Project B | Sprint 2025.5 But this is what we get: Project A * Project A | Sprint 1.2025 (active sprint) * Project A | Sprint 2.2025 (future sprint) * Project A | Sprint 3.2025 * Project A | Sprint 4.2025 * Project A | Sprint 5.2025 Project B * Project B | Sprint 2025.1 (active sprint) * Project A | Sprint 2.2025 (future sprint) * Project B | Sprint 2025.3 * Project B | Sprint 2025.4 * Project B | Sprint 2025.5 Even if we delete the problematic sprint and create a new one in the correct project, in this example above -- we delete the Project A | Sprint 2.2025 from the Project B and create a new one in the Project B, the newly created sprint is incorrectly linked to the Project A. Then it would look like: Project A * Project A | Sprint 1.2025 (active sprint) * Project B | Sprint 2025.2 (future sprint) * Project A | Sprint 3.2025 (future sprint) * Project A | Sprint 4.2025 * Project A | Sprint 5.2025 Project B * Project B | Sprint 2025.1 (active sprint) * Project B | Sprint 2025.2 (future sprint) * Project B | Sprint 2025.3 (future sprint) * Project B | Sprint 2025.4 * Project B | Sprint 2025.5 We check the Sprint ID of the problematic sprint, and they share the same Sprint ID across 2 projects. The same happens if we rename it -- the renamed problematic sprint gets updated in another project. Has anyone ever enountered this? Do you know how to fix this? Thank you in advance!

Does the name include Project Name or it's just as example and they are both name the same in both project ? If someone updated the Sprint field directly and add and issue from project A in the sprint you created in the board for project B, the Sprint for project B will be displayed in project A. As sprints are not related to project but boards. Regards

I haven't tried the JQL query yet. I just had a workaround solution where I moved all of the tickets assigned to Project A's problematic sprint to Backlog created a new sprint with a similar name and moved them to this sprint. I leave this problematic sprint empty for now until this sprint of Project A starts then I'll delete it later. Then I will need to check if the said Sprint will also be deleted from Project B (which will start in 2 weeks). F

@Florian Bonniec Yes, we both sprints of both projects have some tickets assigned to. It only happens to the immediate next sprint (not the sprints after that). I also need to point out that the start date of both Projects are not the same -- the next sprint of Project A starts in 2 days while the next sprint of Project B starts in 2 weeks. No, we always manually create the sprint with the "Create Sprint" button. This time I created the sprints myself.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues with mixed-up Sprints

Dan Ny

Hi,

I encountered a weird problem with mixed up sprints.

We manage multiple projects and each project has its own sprints (sprints are named differently (<Project_Name> | Sprint <Month>.<Year>) or something similar to that. But they all are never the same.

This issue happens again for a second time --the first time it happened was last year but it was too late to fix anything because the sprint had already started.

So, we create several sprints per project beforehand (5 or 6 sprints in advance). But there will always be one of the sprints gets mixed up with another project.

Following are what correct sprint names are supposed to look like:

Project A

Project A | Sprint 1.2025 (active sprint)
Project A | Sprint 2.2025 (future sprint)
Project A | Sprint 3.2025 (future sprint)
Project A | Sprint 4.2025
Project A | Sprint 5.2025

Project B

Project B | Sprint 2025.1 (active sprint)
Project B | Sprint 2025.2 (future sprint)
Project B | Sprint 2025.3 (future sprint)
Project B | Sprint 2025.4
Project B | Sprint 2025.5

But this is what we get:

Project A

Project A | Sprint 1.2025 (active sprint)
Project A | Sprint 2.2025 (future sprint)
Project A | Sprint 3.2025
Project A | Sprint 4.2025
Project A | Sprint 5.2025

Project B

Project B | Sprint 2025.1 (active sprint)
Project A | Sprint 2.2025 (future sprint)
Project B | Sprint 2025.3
Project B | Sprint 2025.4
Project B | Sprint 2025.5

Even if we delete the problematic sprint and create a new one in the correct project, in this example above -- we delete the Project A | Sprint 2.2025 from the Project B and create a new one in the Project B, the newly created sprint is incorrectly linked to the Project A. Then it would look like:

Project A

Project A | Sprint 1.2025 (active sprint)
Project B | Sprint 2025.2 (future sprint)
Project A | Sprint 3.2025 (future sprint)
Project A | Sprint 4.2025
Project A | Sprint 5.2025

Project B

Project B | Sprint 2025.1 (active sprint)
Project B | Sprint 2025.2 (future sprint)
Project B | Sprint 2025.3 (future sprint)
Project B | Sprint 2025.4
Project B | Sprint 2025.5

We check the Sprint ID of the problematic sprint, and they share the same Sprint ID across 2 projects. The same happens if we rename it -- the renamed problematic sprint gets updated in another project.

Has anyone ever enountered this? Do you know how to fix this?

Thank you in advance!

Accepted answers

All comments

Florian Bonniec

Hi @Dan Ny

Are you using JIRA DC or JIRA Cloud ?

On JIRA DC, Sprints are related to board, not project. A bord could cover multiple projects.

Regards

Dan Ny

Hi @Florian Bonniec

Thanks for your quick answer.

Based on the info below, I believe we're using DC

Installation Type	Standalone
Server ID	XXXX-YYYY-ZZZZ-AAAA
Last Upgrade	01/Feb/19 2:31 PM (v6.4.8#64023)

Florian Bonniec

Most likely Project B | Sprint 2025.2 is displayed in both because you have a ticket from both project assigned to it, or at least from project A. It occur when there is the Sprint field in the create/edit screen and someone select the wrong Sprint.

For the naming issue, do you have something that create automatically them ?

Dan Ny

@Florian Bonniec

I just checked our board (of each project), they are different -- meaning each project has it own board.

Project A

Board name Project A board

Administrators Mr. A

Filter

Saved Filter Filter for Project A board

Project: Project A (VIEW)

Owner Mr. A

Project B

Board name Project B board

Administrators Mr. X

Filter

Saved Filter Filter for Project B board

Project: Project B (VIEW)

Owner Mr. X

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

sprint

unknown-hosting-type

problem

jira-unknown-hosting-type

incorrect