Add a Custom Status to FogBugz

This article is meant for Licensed FogBugz. Sorry, but if you are using FogBugz On Demand, custom statuses are currently unavailable.

While we try to include the most common statuses in FogBugz, customers occasionally want to be able to add a custom status of their own. For instance, in situations where the customer has a dedicated quality assurance (QA) team, they may want to add a status of "Resolved (to QA)" to FogBugz to indicate that QA should test the bug fix or added feature. Adding new statuses to FogBugz involves adding new values to the database, as described below.

Warning: Editing the database directly can cause problems with your FogBugz installation. Please back up your database before editing it.

  1. Open the 'Status' table of the FogBugz database.
  2. Create a new row in that 'Status' table with the following values.
    1. sStatus = "Resolved (to QA)"
    2. ixCategory = -1
      • ixCategory should be set to -1 if the new status should be available to all categories, 1 if it should only apply to bugs (e.g. "Resolved (Fixed)"), 2 if it should only apply to features (e.g. "Resolved (Implemented)"), 3 if it should only apply to inquiries (e.g. "Resolved (Responded)")
    3. fWorkDone = 1
      • fWorkDone tells Evidence-Based Scheduling whether time spent on this case should be included in future schedule estimates. Set it to 1 if it should (e.g Fixed or Implemented), or 0 if it should not (e.g. "Not Reproducible", "Won't Implement", "By Design", etc.)
  3. Save the changes
  4. You must now force FogBugz to reload its local browser cache. You can do this by logging into FogBugz as an administrator, going to Settings->Clients, clicking on any client, and clicking OK without editing anything.
  5. To confirm the change, create a test case, then resolve it as "Resolved (to QA)".