Ignite Global Support Home
How can we help?
  1. FogBugz Support
  2. Fogbugz
  3. Database
  4. Data Manipulation

Dealing with Rogue Cases - FogBugz On-Premise


Botond Bajka
  • Updated
Follow

Overview

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.

 

Prerequisites

  • Administrator access to the FogBugz database
  • Full backup of your FogBugz database is executed before proceeding to the steps in this article

 

Diagnosis

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:

http://<YOUR_FOGBUGZ_URL>/diagnostics.asp?sStep=testroguecases

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").

 

Back to the top

Solution

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 you are unable to repair the rogue cases, you can purge them from the database, and reimport them using one of the available tools.

To Fix Rogue Cases

  1. Take a full backup of your FogBugz database.
  2. Download the SQL script attached to the current article.
  3. Update the script: in the first SQL statement use fogbugz, replacefogbubz with the name of your FogBugz database. For example, in case of trial1 database it will become: use trial1.
  4. Run the script against your FogBugz database.

If you have any questions and want to double-check with us before modifying your database contact us. 

Please make sure you have a full backup of your FogBugz database before making any changes. This script irreversibly modifies your FogBugz data, and the ability to restore to a known state will be invaluable should the need arise.

 

Back to the top

Testing

Check for any remaining rogue cases.

If you are unable to repair the rogue cases, you can purge them from the database, and reimport them using one of the available tools.

If you find that you have rogue cases that are not getting fixed by this approach, contact us.

Back to the top

Related Articles

Back to the top