After upgrading Fogbugz from 6.1.46 to 7.3.0 we now have a problem that when a new Case is raised it is given an ID of an already existing Case. The title of the case is changed to the newly created title. Old details relating to the original case remain, with the new case description appended at the end of this information.
We use MySQL for the database, and were using version 4.1.9. It appears FogBugz 7.3.0 does not support this version so I upgraded MySQL to the minimum requirement specified of 5.0.45. Both MySQL and Fogbugz upgrades appeared to go without problem. (on a Windows 2003 Server box)
The FogBugz diagnostics suite does report a few discrepancies as part of the 'Rogue Case Check' but it looks unlikely that this could be the cause of the problem detailed above.
*Case 843 (ECN 20036367 - Modifications to ADEPT60 TADL) has a bad ixBugEventLatest value (It is set to "NULL")
Case 844 (ECN 20036367 - Modifications to ADEPT60 TADL) has a bad ixBugEventLatest value (It is set to "NULL")
Case 845 (ECN 20036367 - Modifications to ADEPT60 TADL) has a bad ixBugEventLatest value (It is set to "NULL")
Case 848 (ECN 20036367 - Modifications to ADEPT60 TADL) has a bad ixBugEventLatest value (It is set to "NULL")*
The 'Check Database' feature reports no problems.
I tried to change the starting case number given to new cases (in accordance with the instructions given here http://fogbugz.stackexchange.com/questions/869/how-do-i-change-the-starting-case-number-in-fogbugz) but this had no effect.
I'm struggling to know how to resolve this problem now so any pointers would be much appreciated.
Further investigation:
It appears the case id number allocated to new cases is not just limited to existing case numbers. It will generate what appear to be random case numbers, and in the case when the case doesnt already exist I receive the following message...
Thanks!
Your case report has been submitted. When it has been fixed, you will be notified by email. Remember, it is your responsibility to check if the resolution is satisfactory and close the case after it is resolved. Case #2696 does not exist or has been deleted.
I created a new database today to see if I got similar behaviour but all the tests I carried out ran perfectly. This seems to suggest my installation of Fogbugz (7.3.0) and MySQL (5.0.45) are configured and running ok. So I am now wondering whether there is a problem with FogBugz's upgrade of my database (from 633 to 743)
In the meantime, I am hoping to downgrade Fogbugz back to 6.1.46 so Fogbugz is usable again. Are there any instructions for doing this?
