You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This question is in reference to Atlassian Documentation: Using JIRA Software for Resource or Portfolio Management: why am I seeing a gap of multiple sprints for a resource in Portfolio, even though there is no other story for the resource and no dependencies?
I just spent quite a bit of time trying to figure this out and what I found was my release start date didn't match my sprint start date on the sprints that were getting skipped. I found that while I had started all my releases on Mondays and ended all releases on Fridays, the sprints I created for each team ended on Fridays but started on Saturdays. The sprints that were getting skipped where the sprints at the start or end of a release where this mismatch was apparent. When set all my releases to end on Fridays and start the next on Saturday just like my sprints, this problem resolved itself.