Remaining Estimate Post Function + Agile Burndown = Not Right

HoneyD November 7, 2014

Hello!

We did a great job on our sprint this week! We completed all our issues and all of our remaining estimates are set to zero. We were very excited to take a look at our burndown chart, but not so excited when we saw this:

2014-11-07 15_33_59-_ Nexus Sprint - Agile Board - DealerPeak JIRA.png

We meticulously looked through every issue for rogue sub-tasks and loose remaining estimates and there was none. We were seriously confused.

The report under the burndown chart in JIRA gave a very important clue. Although issues were being closed, the "Dec." column was not "Dec."-ing, and therefore the "Remaining Time Estimate" column was stuck.

2014-11-07 15_39_36-_ Nexus Sprint - Agile Board - DealerPeak JIRA.png

You may wonder why I would expect that when an issue is completed, the "Dec." column should, in fact, "Dec." Well, we have one of those very fancy Post Functions on our Close Transition, which sets the remaining estimate to zero.

2014-11-07 15_41_35-Transition_ Close Issue - DealerPeak JIRA.png

It seems to me that although this post function may be quite handy, it may not be communicating with the Agile plugin in the way I would expect.

By some miracle, is there anyone out there who can help?

Thank you!

Honey - and the rest of the DealerPeak team

1 answer

0 votes
carlgieringer July 14, 2015

Did you ever solve this? Seems to be an issue with JIRA on-demand still...

Suggest an answer

Log in or Sign up to answer