In our group we have deployed FogBUGZ with MySQL and have been using it for couple of months now. According to the MySQL Control Center, we have a total of 74 cases. But in FogBUGZ, the case numbers for new cases are currently running in 400's.
I can't speak for mySQL, but in MS SQL server, the answer to your question is yes. The AutoNum does not revert down to the next available bug number if you delete the last 20. It just keeps going where it's at.
The reason why it would jump up so high is that the dispatcho mail retrieval program was unsuccessfully submitting cases to your server (maybe their was an email with an extra large attachment) and the case was being entered into fogbugz but the asp page was not OK'ing that it actually made it in. To prevent from duplicate entries the dispatcho program would then tell fogbugz to delete the case if it accidentally did get added to the database (because dispatcho would try again later). If you have your mail checking set to very frequently (in the mailboxes screen) and your server went down or there was a network slowdown or something, this could have been the cause.
Michael H. Pryor
Reply to Karan: The couple of sample cases we manually deleted were like case numbers 2 and 3. The new case numbers continued from where the counter stood last. But we never manually deleted any cases after that.
If the problem is because of too-large emails that take too long to submit to FogBUGZ, it may be possible to increase the timeout settings in IIS beyond the default 30 (?) seconds.
I don't believe the emails to our FogBUGZ mailboxes are huge. Until now they are actually less than 300K.
As soon as Michael gets back from vacation at the end of this week he's going to work on fixing this...
Was this ever addressed? We're running 3.0.5 and have pretty large email attachemnts (screen shots) and have mail pulling very frequently (we have everyone doing QA use email to send in bugz instead of using the web becasue it is easier for the screen shots) and our cases jumped from 235 - 1500 - 1800 very quickly.
I tracked down the problem. An email was sent with a 1.3M attachment to one of our FogBUGZ email boxes. Dispatcho kept trying to publish the email as a FogBUGZ case, but failed. Every time it failed, the case number gets incremented.
What's the fix for SQL Server?
Fog Creek Home