What is the challenge? |
Description
Problem
When epic progress is based on remaining estimate (“Calculate from remaining estimate”), the rollup only uses Detailed estimates on child records. If a child story (feature/requirement) has only an Initial estimate and no Detailed estimate, its work does not contribute to the epic’s rolled-up estimate/progress. This makes epic progress misleading for teams that estimate initially and only add Detailed estimates later (or never).
Current behavior
Child record level: remaining estimate correctly falls back to Initial estimate when there is no Detailed estimate. Epic rollup level: only children’s Detailed estimates are included; Initial estimates are ignored.
|
What is the impact? |
Epic progress bars under-represent work for epics whose child records have only Initial estimates. Teams that primarily use Initial estimate for sizing cannot rely on epic progress unless they duplicate estimates into the Detailed field.
Why this matters
Aligns epic progress with how teams actually estimate (often starting with Initial only). Reduces duplicate data entry. Makes epic progress bars a more accurate and trustworthy signal for stakeholders.
|
Describe your idea |
Requested improvement
Please add a way for parent records (especially epics) to:
Roll up from Initial OR Detailed estimates, or Use Initial estimate as a fallback when Detailed estimate is blank on a child record.
This could be:
A workspace/record setting for estimate rollup behavior (e.g., “Roll up from: Detailed only / Initial only / Initial + Detailed (with fallback)”), or A global behavior change where parent rollups mirror the child-level remaining estimate logic (using Initial when Detailed is blank).
|
