It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sprints undesirably shared over projects

I have a couple of projects, configured a "Classic software". Each project has a board (i know a board is not per connected to a project) and it's own backlog. Now the issue is that the backlogs some sort of seem to have connected: i see sprints that are made in the backlog of Project X on the backlog of project Y; although they both only have issues that are in the project they're in. But, when renaming one of these sprints (either in Project X or Y), it is changed in the other backlog as well. How do i disentangle this?

1 answer

1 accepted

0 votes
Answer accepted

Hello @Koen_Roumen

Welcome to Atlassian Support.

Per your description, it seems that the same Sprint is displaying on two different projects (X and Y), although it should only be displayed in project X. Is that correct?

Please, allow me to provide you with some details on what can cause this issue so we can be on the same page: 

Just like Boards, Sprints are completely independent, so it can be added to multiple Projects or Boards, just like described in the KB below:

Sprints appearing on multiple boards in Jira server 

That being said, a Sprint will be displayed on a board every time someone added a Sprint to any issue returned by that board filter. Here are some of the actions that could cause this behavior:

1 - An issue is moved from one project to another. If the Sprint from the previous project is not cleared from the moved issue, the sprint related to the issue will start displaying in the new board

2 - The board filter is edited, returning the issues also included in a different board and with different Sprints

3 - Any issue was manually added with the Sprint of a different project

The steps to fix it would be:

- Navigate to the board where the Sprints are unexpectedly appearing > board settings > Edit filter query

- At the end of the filter query (before the ORDER parameter), add the following parameter with the name of the Sprint that is wrongly displaying in the board and run the query, but don't save it:

and sprint = yoursprintname

- Now, you have the issues that are wrongly configured with the Sprint. You can change it to the correct Sprint of your project or clear the field, optionally using the bulk operation feature.

Let us know if you have any questions.

Very clear answer Petter, thanks a lot!

You are welcome, @Koen_Roumen

Have a nice week.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Metrics Fun: 2019 in Review

Hello, Atlassian Community!  I thought it would be fun to do something different for my teams' last retrospective of 2019 so I'm planning to do a "year in review" with info-graphics.  Wha...

1,892 views 10 14
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you