Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9164

Sub-task hours estimate not reflected in planning and reports

      We have configured our agile boards to do estimation statistics on "Original Time Estimate" and Time tracking on "Remaining Estimate and Time Spent".

      Unfortunately the planning screen does not show hours summarized also from sub-tasks. If you do planning (Plan screen) only on sub-task level than the field for estimate (total estimate time) is blank. See attached screenshot.
      Also problem here is that if you do not resolve task/sub-task in eg: Sprint 1 and you put it into Sprint 2 it will show original estimate (the one that's done on task level) instead of remaining time.
      The same applies to Report screen - Burndown chart. The sum of remaining hours for sub-task hours is not there. Original estimate is used instead.

            [JSWSERVER-9164] Sub-task hours estimate not reflected in planning and reports

            Cathy S made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 884512 ]
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.01
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2852690 ] New: JAC Bug Workflow v3 [ 2935982 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542753 ] New: JAC Bug Workflow v2 [ 2852690 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549348 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542753 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

            Hi Peter,

            The referenced article discusses the advantages of using story points instead of hourly estimates. 
            Unfortunately it is not relevant in case JIRA user does not use story points in the JIRA Board. Such functionality is officially supported by JIRA. E.g. JIRA supports the following selections in the Board:

            Estimation Statistic set to "Original Time Estimate"
            Time Tracking set to "Remaining Estimate and Time Spent"

            In such case the expectation is that the Burndown chart "Remaining Time Estimate" will include time logged in sub-tasks. I see this is the case in JIRA v7.2.1 so one issue reported in this defect is addressed.

            Another expectation is that the time entered in "Estimated" field in sub-task before the sprint starts will be accounted for in Velocity report. The time estimates reported in sub-tasks of a Story before the sprint starts are a part of the estimated effort of the Story before the sprint starts. By definition Velocity should include complete effort estimate for a Story done before sprint starts. Including only part of the estimate is a defect in JIRA v7.2.1 which makes it impossible to use officially supported JIRA functionality (Estimation Statistic set to "Original Time Estimate" and Time Tracking set to "Remaining Estimate and Time Spent").
            Please note that the same effort in time cannot be estimated in Story and tracked in sub-tasks because with such usage it is double counted by the tool. 
            The mechanism of estimating effort in story points in Story and tracking time in sub-tasks works fine but it does not apply for users who want to use time tracking for both estimation and tracking.

            Thanks,
            Dariusz.

            Dariusz Tomaszewski added a comment - Hi Peter, The referenced article discusses the advantages of using story points instead of hourly estimates.  Unfortunately it is not relevant in case JIRA user does not use story points in the JIRA Board. Such functionality is officially supported by JIRA. E.g. JIRA supports the following selections in the Board: Estimation Statistic set to "Original Time Estimate" Time Tracking set to "Remaining Estimate and Time Spent" In such case the expectation is that the Burndown chart "Remaining Time Estimate" will include time logged in sub-tasks. I see this is the case in JIRA v7.2.1 so one issue reported in this defect is addressed. Another expectation is that the time entered in "Estimated" field in sub-task before the sprint starts will be accounted for in Velocity report. The time estimates reported in sub-tasks of a Story before the sprint starts are a part of the estimated effort of the Story before the sprint starts. By definition Velocity should include complete effort estimate for a Story done before sprint starts. Including only part of the estimate is a defect in JIRA v7.2.1 which makes it impossible to use officially supported JIRA functionality (Estimation Statistic set to "Original Time Estimate" and Time Tracking set to "Remaining Estimate and Time Spent"). Please note that the same effort in time cannot be estimated in Story and tracked in sub-tasks because with such usage it is double counted by the tool.  The mechanism of estimating effort in story points in Story and tracking time in sub-tasks works fine but it does not apply for users who want to use time tracking for both estimation and tracking. Thanks, Dariusz.
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909185 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549348 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 743108 ] New: JIRA Bug Workflow w Kanban v6 [ 909185 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 535889 ] New: GreenHopper Kanban Workflow 20141014 [ 743108 ]

              Unassigned Unassigned
              cc4d5d6c4288 Lubomir Pipiska
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: