Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to start sprint due to active sprint in another project

I have a master project MASTER with a filter that includes 4 other projects: SUBA, SUBB, SUBC and SUBD. I want to create sprints in all five projects and view them in the MASTER board. However, I am not able to start the sprint in the MASTER project and the explanation given is that there is an active sprint in SUBD. It appears as if the sprint in SUBD belongs to both SUBD and MASTER, and I am not able to start a new sprint in either of these projects due to the same active sprint.

The active sprint in this case is named "SUBD Sprint 2".  When I create a new sprint in MASTER (or in SUBD) it is automatically named as "SUBD Sprint 3" in both projects. 

Is there a way to avoid this and create a MASTER Sprint instead?

1 answer

0 votes
Kevin Bui Atlassian Team Jan 12, 2020

Hi @Sigurd Saue,

I'm not sure if this is viable for you at all, but one option I can think of is to plan and start the sprint from MASTER, and then use Quick Filters to swap between SUBA, SUBB, SUBC, and SUBD. But for this to work, SUBA, SUBB, SUBC and SUBD would have to be labels or components, rather than boards.

Hope that helps!

Thanks for your reply, but I'm not sure it will do the trick for us. SUBA - SUBD are all NextGen projects that have been running for a while, while MASTER is a classic project since that's the only one that allows us to include issues from several projects in one board.

I might be missing something essential about the relations between boards, labels, components and projects. I notice that your option does not use the word "project" at all.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events