Hi @Natalie_Mihigo1 and welcome to the community! This is by design as sprints are not tied to projects or project boards.
An example use case of where this is a desirable feature is a situation where you have a complex application made up of multiple micro services. Each micro service is managed on a specific project to enable uniquely linked code repos. However, only one or two teams actually manage the overall application. In this use case, it would be desirable for the sprint to span multiple projects so that the team can track the work across the application in a single sprint rather than trying to navigate one sprint for every micro service.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.