Why jira portfolio moves one task to next sprint while still capacity available?

[Jan Festjens]

Hi,

I have a portfolio plan which seems to keep setting one specific task in a next sprint, while there is still capacity available in the previous sprint. How does this happen?

For information, I'm able to statically assign the item to the current sprint (blue). But when I choose calculate, it creates sprint 3, while in sprint 2 there is still capacity available (red).

image2017-1-25 17:5:27.png

image2017-1-25 17:6:26.png

[Jan Festjens]

Hi Aaron,

thanks for helping me out here. 

1. we do estimations in time. It's not estimated yet, so in JPO I have a default of 0.5 days setting, while there is still a few days open capacity, this should (I think) be enough.
2. No, I disabled filters in the JPO live plan and the boards that are used as source are also unfiltered.
3. When I add it manually to the active sprint, it works fine. There is no over assign to my capacity.
4. There is no earliest date set. 

Regards,

Jan

[Aaron Steinmetz]

1. How many points is DEV-662?
2. Do you have any filters applied (i know, i know it shouldn't matter but it's becoming a #1 on my checklist of sanity when using Portfolio... it changes things without you realising sometimes).
3. When you assign it to sprint 11 manually, does it over assign your capacity?
4. Is there an earliest start date on your dev-662?