FogBugz cases have a slight possibility of "going rogue," meaning that the cases will be unreachable in FogBugz. This usually happens if you have deleted data directly from your database or imported data from another tool and did not fill out all the FogBugz database fields. FogBugz should still work fine, but this is something you will want to try and fix directly in the database. We recommend checking for the existence of (and fixing) rogue cases before upgrading or migrating your data to another server.
FogBugz version 8.8.55 and below have a built-in mechanism that checks for rogue cases. You can run the diagnostic check by navigating to this URL:
The output will list any rogue cases found, as well as the problem with each case.
FogBugz 8.15 and above (FogBugz On-Site, Manuscript On-Premise, and FogBugz On-Premise) do not have this functionality. You can identify the rogue cases since they are visible in the search listings. However, the case would not open ("case not found").
Fixing Rogue Cases
We have prepared a SQL script that resolves the most common issues with rogue cases. We first attempt to repair any inconsistent data using the case history and make reasonable guesses for easily-changeable fields like Project, Area, Status, etc. If we are unable to repair the rogue cases, we purge them from the database.
To Fix Rogue Cases:
Download the SQL script for your database provider below.
Take a full backup of your FogBugz database.
Run the script against your FogBugz database, and then re-run the rogue case check.
If you have any questions and want to double-check with us before modifying your database or find that you have rogue cases that are not getting fixed by this approach, contact us.