I have an issue A which has an estimate of 2 hours and and issue B which has an estimate of 2 hours. The team the work is connected to has enough capacity to do the work.
When I add an dependency (Issue B is depependent on Issue A), Issue B is scheduled ONE DAY LATER (visually "behind on the same level" as Issue A), although there should be enough capacity for Issue B on the day where Issue A is scheduled I would have assumed (which would mean for me a visual representaton "below" Issue A on the same day.)
Can somebody explain this behaviour? Does a dependency always mean, the issue can only be started the next day? Or what am I missing?
Thanks for your help!
Hi @Sascha Heckelei,
By default dependencies must happen on a different time unit (Different sprint for Scrum teams, different day for Kanban teams).
The main reason is that Portfolio does not schedule below that time unit, so as far as Portfolio is concerned this issue won't be done until the end of the day which means dependent items can only start as early as the next day.
You can change this behavior in your plan configuration -> Scheduling -> Dependent story constraint
You can read more about it in the docs here
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events