23ef3e30d63c I don't agree that this ticket should be closed: the filter works in the "Active Sprints" section, but the "Recent Sprints" is still not filtered and so this request has not been fulfilled.

In the Sprint field it is possible to only include sprints from the current project, and you can see the Board associated with each Sprint:

The year is 2022, the earthlings are suffering from hordes of small bugs coming from big companies...
only a hero can save us... 

Anthem for the Year 2022

We are the youth, we'll take your duplicated sprint away
We are the youth, apologize for another duplicated sprint day
We are the youth and programmers are so sure
We are the youth and we are knocking on bugs door

Never knew we were using a software
With a code that could be so sure
Never knew we were using a software
With a bug that could be so small
Never knew we were using a software
And the software could be open source
Maybe we don't wanna use this software
Where our time is so short
We'll make it up to you in the year 2022 with

...

We'll make it up to you in the year 2022
Build it up for you in the year 2022
Make it hard for you in the year 2022

– woodenchair

Year 2021. We are still facing the same issue. It affects us a lot. How many votes are required to take an action? 

Vote it up people!

Totally agree with Mark: Having this functionality to only show sprints for the project would save us from a lot of confusion. 

This is a must have feature.

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.