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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,289
Community Members
 
Community Events
176
Community Groups

Empty sprints in plan (Portfolio)

Edited

I have built a roadmap in plan view (portfolio) which consists of several teams.

I have manually allocated teams to the various epics and manually placed the tickets in future sprints to avoid auto forecast in delivery planning. 

I have also defined a few versions with certain dates.

Some dependencies are defined but a lot of the epics are not dependent on anything.

The problem I see is that one of the teams has one empty sprint in the middle of their workplan, just next to active sprint. 

Tried to change the sequence of the sprints or remove the dependencies but the couldn't fix it.

Any idea on how to resolve this? 

1 answer

0 votes

Hello @Emir.Ipekci ,

I would be happy to take a closer look and I have a few questions about the setup. 

You noted that you had:

"manually placed the tickets in future sprints to avoid auto forecast in delivery planning"

And that you also have:

"one of the teams has one empty sprint in the middle of their workplan, just next to active sprint" 

From this explanation, it sounds like the sprint may have been created and no issues were ever manually added to it, or the issues that were in the sprint have been moved to another sprint in planning, with an additional possibility of the sprint being closed with no issues present.  

The question I have is, is this sprint just empty and unplanned that you want to remove the sprint, or are you trying to schedule issues into this sprint and expecting to have the sprint populated with issues?

If you want to remove the empty sprint check out the Documentation "Delete a sprint".

If you need to get issues added to the sprint as you have the issues added manually check out "Assigning issues to sprints", to get issues added to the empty sprint, and if the sprint is empty and completed you would want to look at "Reopen a sprint" first as you cannot add issues to a closed sprint, only an active or future sprint.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events