GreenHopper Documentation

JIRA Agile 6.3
GreenHopper 6.2
GreenHopper 6.1

More...
 

 

GreenHopper Knowledge Base Resources

Say hello to JIRA Agile (formerly GreenHopper). Learn more.
For the latest content and updates visit the new JIRA Agile Knowledge Base.

Skip to end of metadata
Go to start of metadata

Symptom

Burndown chart and version time-tracking statistics of existing projects are different after upgrading to GreenHopper v5.2. The main difference is on the "Initial Remaining Hours" of burndown chart and "Time Estimate" value of version time-tracking statistics.

Cause

This relates to a bug fix ticket implemented in GreenHopper v5.2, GHS-1902. Prior to v5.2, the "original estimate/remaining" shown in GreenHopper statistics and burndown charts was calculated based on the current "original estimate" of all associated issues, no matter whether the "original estimate" is adjusted to after the sprint starts. This was changed based on the assumption that sprint planning is completed no later than the end of the sprint's start date. GreenHopper therefore doesn't count in any change of "original estimate" after version's start date to make its statistics helpful in showing whether or not improvements in the accuracy of sprint planning estimates are required.

Examples:

  • If the issue's "original estimate" is changed after sprint's start date, GreenHopper v5.1 will count this change into the calculation of "original estimate/remaining" of burndown chart and version statistics, however v5.2 does not.
  • If a new issue is added into the new version after sprint's start date, GreenHopper v5.1 will count this new issue into the calculation of "original estimate/remaining" of burndown chart and version statistics, however v5.2 does not.

For the more explanation and demonstrated scenarioes, refer to How Hour Burndown Charts Relate to Time Tracking in JIRA.

Limitation

There's a known limitation of v5.2 "original estimate/remaining" statistics, which's disobedient from GreenHopper's assumption - if an existing issue is moved from 'unscheduled' or other versions to this version, it will still be counted into the calculation of "original estimate/remaining" of burndown chart and version statistics. This has been caught by GreenHopper development team, and will fix it in the later release.