nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint still has capacity but issue is scheduled in next sprint

sebastianhsu

I have a sprint (Sprint2) which there is still 24 hours free capacity.

However, another issue which only has 8 hours is scheduled to next sprint (Sprint3) instead of Sprint2.

Here is the information for these 2 issue, wmam-316 is the one in Sprint2, wmam-317 is the one in Sprint3 and can't be scheduled to Sprint2. There is no dependency between these 2.

Anyone has any clue why does this happen?

Comments

sebastianhsu

Answer for myself, it turned out that if earliest start is greater than the date that sprint start, it will be pushed to next sprint.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

advanced-roadmaps