Remaining Estimate Zeroed out not reflected in previous versions

Scott Latsa February 9, 2012

When we zero out the remaining time (automatic when we close an issue) and it's after the version end date, the burndown chart does not reflect accurately. Can you change the "transaction date" on remaining time kinda like Logging Work for a previous release/sprint? For example, the sprint ends 2/2 (version end date) and we close out the user story on 2/9 (release date). The remaining time get zeroed out, but time stamped with today's day 2/9. So, the burndown chart doesn't reflect this because it queries dates up until 2/2 Version End Date.

2 answers

1 accepted

2 votes
Answer accepted
Matthew Hunter
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 14, 2012

Hi Scott,

When you close out the issue and log the remaining work you can set the 'Date Started', if you set this to before or on the end date then the Burndown chart should reflect that the work has been completed.

You can also edit any work entry and change the start date after you've already submitted it. You can do that via the 'work logged' tab on any JIRA issue by clicking the edit pen as you would when you change any comment. :)

Cheers,

Matt

0 votes
Scott Latsa February 14, 2012

Matt,

Thanks for the answer. Editting the last "work logged" is an excellent idea. Showing how your team has approached the design of GH really helps. Much apprecitate!

Thanks,

Scott

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events