FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Loss of 50% date value from Status Report

I changed the release date of a project from a specific date to (none).  When I went to the Status Report, the Upcoming Releases section reported that that release date had not been calculated yet.  However, I do have Ship Date over Time graph that shows the history of estimates, so I'm not sure why this changed.

I did also enter a new case for that release and enter a couple of missing estimates for that release.

The order of open releases has not changed as a result of my changing the release date.
Charlotte M Send private email
Tuesday, December 11, 2007
 
 
The release dates in the "Upcoming Releases" section are only calculated once a day because they require extra computing power (that's when FogBugz runs the Monte Carlo simulation 100 times to get a best estimate).  The "Ship Date over Time" graph is a snapshot of one possible Monte Carlo run, so sometimes those can be out of sync.  I think that the changes you made may have put it in an uncalculated state, and it should show up again with a 50% date tomorrow after the overnight calculation.

Changing the release date to (None) should have moved the released to the end of the list, so I'm not sure why the order didn't change.

Let's check back tomorrow and see if it looks correct then.
Eric Nehrlich Send private email
Wednesday, December 12, 2007
 
 
All three releases for this project have a release date of (none) so that's why it didn't move to the end of the list.  There's no reason that changing the anticipated due date should affect the projected completion date though.

I checked today and it still says "Not yet calculated".  However, I checked other projects, some of which do have release dates and most of which don't, and they all say "Not yet calculated".  So I don't think chaging the release date caused this situation, but rather than I hadn't run a report in a couple of weeks and just discovered the problem yesterday.

We are currently running 6.0.25 and we did upgrade (from .23, I think) during that time interval.  We also had some power outage issues that caused temporary problems on that server though I don't think it affected the database.
Charlotte M Send private email
Wednesday, December 12, 2007
 
 
Hrm.  Do you have email working with FogBugz right now?  The FogBugz Maintenance Service which does email is also supposed to update the reports overnight.  Can you try restarting that service?

Can you also check if there's a message that says "Some errors have occurred in FogBugz" at the top of your FogBugz page?  Please tell us what those errors are so we can think about what might be happening.

Lastly, can you look in the FogBugz database in the Setting table and see what the sValue is corresponding to sKey=dtLastDailyTask?  That records the last time the daily task (when it does estimates) ran successfully.
Eric Nehrlich Send private email
Thursday, December 13, 2007
 
 
No, we did not have email working either.  However, we upgraded to .39 yesterday and then the emails started working and the 50% estimates were back.  Also I noticed that the time series for the estimates had not been calculated for a week.  Looks like everything is fine now.
Charlotte M Send private email
Thursday, December 13, 2007
 
 
Glad to hear that things are working now.  I'm guessing the maintenance service got turned off somehow, but when you upgraded, it kickstarted it and got it working again.  Let us know if you have any other issues?
Eric Nehrlich Send private email
Friday, December 14, 2007
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.