This suggestion is a duplicate of the linked issue fixed in 8.11.0 version.

I would also like this feature. It's a major annoyance to have to filter through sprints from other projects when selecting from this dropdown.

Isn't this a major security hole? If one works at a large enough organization there will be projects other areas should know nothing about.  There will be some projects others don't have enough of a government security clearance to view. By looking at the sprint names they can learn a great deal about the project and its progress.

Are there any updates on this? This feature is very much needed.

Are there any updates on this? This feature is very much needed.

As a workaround, I add the project code to the sprint name to avoid confusion. 

For example:

• Agile Board 1 for Project JAZ: 
  1. JAZ sprint 1
  2. JAZ sprint 2
• Agile Board 2 for Project YEZ
  1. YEZ sprint 1
  2. YEZ sprint 2

Using this method when searching for the active sprint, you type the project code first and then only the sprints for the current project appear.  This method is subject to user error and I have to manually correct the sprint values for a small percentage of stories in every sprint, but it does help reduce confusion.

I may be not considering some aspects of this but what about if there was a flag that if checked, would only show the sprints for that project(s) for the board.  If the flag isn't checked then the same behavior as today for those groups that have sprints that cross multiple projects.  

Having this functionality to only show sprints for the project would save us from a lot of confusion.  Today we have some sprints that get modified that cross projects and then it surprises other developers.  And the reverse is true too that some scrum masters can't edit sprints that are part of their project but the sprint spans projects where the scrum master doesn't have the access on the other projects.  

We have had the same problem as Kevin R describes above.  People at my company have lost confidence in JIRA, since the state of sprints is often wrong.  Please make this fix soon or we are going to have to move to another tool. 

This is a big deal to us as well. Hopefully this makes it into a future release soon. Thanks.

Hello,

I recently bumped into that problem. As for Joshua, my company has a rather large jira with many projects and multiple teams using sprints.
We ended up with two teams using the same sprint without realizing it. They couldn't act on the sprint because of missing admin rights from the other project. I scratched my head for some time before I figured the issue out. And once I did, it took me some more time to untangle the situation.

We are now prefixing sprint names with the project name, which brings me to the following suggestion:

Why not make it more explicit where the sprint is coming from ?
For example, the suggestion list could look like this:

=Agile board name 1=
Sprint 1
Sprint 2
=Agile board name 2=
Sprint 1

I'm assuming sprints are bound to an agile board here, not sure if that's how it works in the backend though.

Thanks.