Details
-
Suggestion
-
Resolution: Won't Fix
-
2
-
Description
Issue Summary
Auto-scheduling only considers issues with estimates. However, when inter-dependant issues have manually been assigned dates that conflict (i.e. the issue B depends on issue A but issue B has been scheduled to start before issue A has completed) the auto-schedule algorithm does not adjust those dates if the issues do not have estimates.
Steps to Reproduce
- Create a plan
- Create Issue A
- Create Issue B
- Make Issue B depend on Issue A
- Set start and end dates on both issues so that Issue B is scheduled to start before Issue A is scheduled to end
- Ensure that no estimates are set on either issue
- Run auto-schedule
Expected Results
The scheduling algorithm should recognise the dependency and conflicting dates and adjust them accordingly.
Actual Results
The dates for the issues are not changed
Workaround
Add estimates to the issues.
Attachments
Issue Links
- relates to
-
JSWCLOUD-20574 Unestimated child issues causes incoherent dependency scheduling
- Gathering Impact
-
JPO-19877 Loading...
-
JPO-14732 Loading...
- was cloned as
-
JSWCLOUD-25414 Auto-scheduling on issues with dependency conflicts but no estimates are not rescheduled
- Gathering Interest