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?
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:
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.
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. Do you structure your teams i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot