Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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.

Sprint Issue.png

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

1 answer

1 accepted

0 votes
Answer accepted

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! 

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!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

64 views 1 2
Read article

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