As larger stories and tasks are broken down into technical subtasks, Dual Point Estimation helps teams ensure that subtask scopes remain aligned with the parent commitment.
When an issue has child subtasks, Dual Point Estimation sums their estimates independently:
Subtask Total (Low) = Sum of all child Low estimatesSubtask Total (High) = Sum of all child High estimatesIf a subtask has a Low estimate but no High estimate, its Low estimate is used for both bounds during summation.
Comparing the sum of subtasks to the parent task's estimate yields one of two states:
When subtask estimates sum to less than the parent's estimate, the panel displays a green confirmation:
Status: Subtask total is within the task's estimate.
Unallocated (Low): 1d
Unallocated (High): 2d
Why this is healthy: In agile planning, having unallocated time on a parent ticket is normal. It represents buffer for emergent bugs, testing, integration friction, or tasks that have not yet been broken down.
If the sum of subtasks exceeds either the parent's Low or High estimate, the app flags an immediate error:
Status: Subtask total high estimate exceeds task's high estimate.
Exceeds by: 2d
In this situation, the estimate diagram bar turns red, and the issue is tagged with the Subtasks Estimate Too High problem filter.
This alerts developers and project leads to one of two planning realities:
Time tracked in Jira is aggregated across parent and child tickets: