We've finished a sprint/iteration and all issues assigned to that version have been marked as resolved with 0 time remaining. However the version still shows 1w remaining?
Why is that?
GreenHopper timeboxes the timetracking statistics between start- and end date of the sprint. Both are GreenHopper specific values. So if work is logged after the end date of a sprint, it won't be taken into consideration for the stats. You could try to backdate a worklog and set the remaining estimate to zero, or correct your sprint end date, because work was still done afterwards.
There must be at least one issue assigned to that version with time on it. You may not see the issue in Greenhopper because of the context's you are using.
I would take a look at the version workload or similar reports for that version in the Project screen, you may find it then. Or use JQL to find all issues for that version with remaining time > 0
We're seeing this as well with GH 5.8.
Our sprint contains 17 issues, each of which is in GH's 'Done' column on the Task-Board and has a zero Remaining Estimate and work-logs dated between the sprint's start- and end-dates. There are no work-logs on the actual end-date.
'Time Estimate' is displayed as 45d, and 'Time Spent' as 33.05d. Both are correct. GH is displaying 'Time Remaining' as 4.8d, however, and I can find no explanation for this.
There are no cards for this sprint which are not being displayed, the Version Workload Report comes back with zero time remaining and to reiterate, no work was logged after the end-date of the sprint. In fact, no changes were made to any of the issues after the end-date.
We are using the built-in 'Default' context to view the Planning-Board and we're looking at it in Version mode. Two of the cards do not have a Resolution at present, but their Original Estimates and Remaining Estimates are all zero, and their work-logs only add up to 1.25d.
Can anyone shed any light on what's going on here?
The hour burndown chart offers a tool called Timetracking Analysis which gives detailed information about how the values are calculated, based on the JIRA change history. Maybe that can shed some light on where GreenHopper gets the remaining time value from for your sprint.
Log Work Utilities add-on allows to clear remaining estimate on issue close/resolve without a need to modify workflow: https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.log-work-utilities/server/overview
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs