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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

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
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

171 views 6 7
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