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,718
Community Members
 
Community Events
176
Community Groups

Recalculating in Portfolio assigns sprints that are in the past

I have a large portfolio plan with over a dozen teams and about 15 initiatives.  I set custom sprints for each team because they each have their own sprint schedules and sprint names.  I set them as fixed and included the start and end dates. I only included forward sprints from the time I set up the plan.

Now whenever the plan recalculates, some of the stories are assigned to sprints that are in the past, even when the status is in Backlog and they're not estimated.  This makes the plan look much more optimistic than I should.  I've been fixing those manually but it's a lot of tedium. Am I doing something wrong or is this a bug? Should I be deleting the custom sprints after they are closed?

 

1 answer

0 votes

Hi Marianne, JIRA Portfolio currently doesn't really know a concept of past/closed sprints, it just schedules from the start date of the plan. The start date is determined in the following way: 

  • If a plan update has been run, then the schedule starts from the last plan update date (Plan > Update from date)
  • If no update was done yet, but there is a release with a fixed start date, the schedule starts from the start date of the earliest release
  • Otherwise the plan starts from today

Basically all sprints that are defined after the the schedule starts, are taken. 

The intended process is to regularly run a plan update (Plan > Update from date), e.g. after every sprint, or weekly. With that, you set a new start date for the plan, i.e., schedule whatever is remaining from the beginning of the next sprint or week. Fixed sprints that are before that date will then be ignored.

The alternative is to indeed just delete the custom sprints from the plan.  

 

 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events