Why are other projects sprints visible as options to select in our project in Next-Gen?

[Britt Cromie]

We have just created a new project within our organisation who is already using next gen for projects. We can see all of the other projects sprints when creating new tasks/stories and vice versa. 

I'm struggling to find results on others questions on this in the community. There isn't anything I can find in the configuration to hide other projects sprints.

See example below - the only sprint that belongs to our project is the highlighted line.

Any help on this would be much appreciated, we want to avoid any confusion and incorrect allocation of tasks to the wrong sprints.

[Walter Buggenhout · Accepted solution]

Hi @Britt Cromie,

Your observation is correct. Sprints are accessible across boards and there are definitely use cases where this is a good thing (e.g. for teams working across multiple projects, like many - if not most - teams do).

Having said that, there is a feature request to improve on this in the backlog: JSWCLOUD-10805. It is a long standing one, so it also mentions the advised workaround to use a naming convention for your sprints, so they clearly reference the project or board the sprint belongs to. That already seems to be the case more or less in your instance, but you may standardise the naming a bit more so search becomes easier.

I wish I had better news, but still hope this helps! 

[Britt Cromie]

Thank you for your suggestion Walter. We are currently using this method to differentiate the project it belongs to, it just looks messy.

Hoping to see a fix some time soon!