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; } } }

Auto-schedule overbooking sprint

Anita Cacic

Hi all,

I have created a plan with following setup:

issues grouped in epics
added estimates and team
created team with 1 week iteration length and 37,5h capacity
used only one dependency

I have turned on sprint capacity view and used auto-schedule, as a result I have a plan that looks like this:

Screen Shot 2021-03-10 at 15.45.52.png

I wanted to try out manage sprint capacity option that was described here so I changed it for Sprint 1 to be 3 days instead of default 5.

Screen Shot 2021-03-10 at 15.48.43.png

By clicking on Auto-schedule I would expect work that is currently in sprint 1 to be moved to the following sprints. What actually happened is that all work is assigned to Sprint 1 and it gets even more overbooked.

Screen Shot 2021-03-10 at 15.52.15.png

This are the options I used on Auto-schedule:

Screen Shot 2021-03-10 at 15.52.02.png

What is causing this issue? Am I doing something wrong?

Comments

Dave

Hi @Anita Cacic ,

Thanks for raising this question.... we've had a quick investigation and it seems like this is a bug. It does work as expected for story point estimation but not for time based estimation. We're going to do some further investigation and verify where the problem is and resolve this issue. We really appreciate you bringing this to our attention and are very sorry for the inconvenience that this is causing!

Regards,

Dave

Anita Cacic

Hi @Dave thank you for your answer. I would highly appreciate if you could get back to me after further investigation with expected resolution date. It is important to me so we can start using this feature across our organisation.

Regards,

Anita

Dave

We've raised the following issues for this problem on both Cloud and Server platforms:

Unfortunately at this stage I can't comment on how quickly we'll be able to get a fix out for this, but by watching these issues you should be able to track progress.

Regards,

Dave

Aaron Collett

How could this possibly be considered a low priority bug, isn't it a key element of advanced roadmaps?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps