From customer feedback it would seem that it is not clear that unestimated issues that block other issues will not have an impact on the scheduling of the blocked issues. There appears to be an expectation that the target end date of an unestimated issue will impact the scheduled start date of blocked issues when this is not the case. Another issue (https://jira.atlassian.com/browse/JPOSERVER-2323) has been raised to make some changes to the scheduling algorithm, but it might be prudent to update the existing documentation in the meantime to clarify the situation.

These the suggested pages to consider improving (although there may be others):

• https://confluence.atlassian.com/jiraportfoliocloud/scheduling-unestimated-items-based-on-default-estimates-844236853.html
• https://confluence.atlassian.com/jiraportfoliocloud/add-target-start-and-target-end-dates-868977060.html

Steps to Reproduce

1. Create a project with issues A and B
2. Make issue B blocked by issue A
3. Create a plan for that project
4. Give an estimate to issue B
5. Give target start and end dates to issue A
6. Click "calculate" to schedule the issues

Expected Results

It could reasonably be expected that issue B will not have a calculated start date that is before the target end date of A (because it is a known date).

Actual Results

B will start as the same time as A (because A is not considered in scheduling because it has no estimate).

Workaround

Give an estimate to issue A.