Portfolio Roadmap New Experience. How to handle dependencies within one sprint?

[Georgii Lumpov]

I'm using Portfolio with the "New experience" turned on.

I have two stories with a dependency between them. The team plans both of them into the same sprint which is OK since the team plans to complete both stories in one time-frame.

But when I press Optimize, I see a warning. It says there is "Dependencies Ignored".

It looks like the logic is like this

IF an issue has a dependency THEN the dependency HAS to have its target end date BEFORE the dependent's target start date.

This seems to limit flexibility :( With this logic I have to either remove dependencies, which is not desirable, or to somehow filter the warnings, to figure out which of them are false-positives to be ignored (like above) and which are the real issues to look at.

Am I misusing the tool somewhere?

[Dave · Accepted solution]

Hi Georgii,

Thanks for raising this point. You're right that this is a problem with the dependency validation logic in the UI being too aggressive.

This will be resolved before we GA the new planning experience such that if the issues are assigned to the same sprint that they will not show dependency warnings in this situation,

I hope this helps,

Regards,

Dave

[Georgii Lumpov]

Hi Dave, this will definitely help. Thanks for your quick answer here.

As an option to consider - maybe it makes sense to have this logic configurable with a check-box in the Plan settings. Something like "Do not flag dependencies within same sprint".

Regards,
George.