FogBugz is the project management and issue tracking software used for projects at UWSC. This article describes how to filter and track cases, and submit bugs using FogBugz.

Fogbugz provides a high-level overview of the FogBugz system:

• A Quick Introduction to FogBugz on Vimeo

Navigating FogBugz:

All FogBugz pages share the same toolbar:

From any page, click on "Cases" to view a list of cases. You will see a case list that looks something like this:

 

From this screen you can filter cases by many attributes by clicking on "Refine Further" and expanding filter categories and selecting the desired filters from the dropdown box, as pictured below:

You can save your frequently-used filters for later by clicking "Save" and giving your filter a name, such as "My Project." You can then access that project easily by clicking on the "Cases" drop-down menu and selecting that filter:

 

You can then filter cases by left clicking on the table headings. You can add more columns of data to filter by clicking on "Select Columns." You can add new cases quickly by clicking "Add Case."

Submitting Bugs/Cases:

You can submit cases/bugs in FogBugz easily from any screen by clicking on "New Case."

The bug submission screen allows you to customize many details about the case you are submitting:

 

1. Title
   1. Be concise and descriptive.
   2. Include a unique identifier for the location of the issue (e.g. item number in CASES). 
2. Project
   1. Select the project that you want to submit the case to. 
   2. FogBugz "saves" the last project you were working on, so if you want to switch projects, you will need to select the new project.
3. Area
   1. Select the area of the project this case/bug applies to.  If none apply, select "Misc."
4. Milestone
   1. Generally not used at UWSC.
5. Category
   1. Choose a category that describes your case.
      1. Bugs are issues that need to be fixed, like programming errors, typos, or production problems. 
      2. Features are requests for new functionality or the addition of something that does not yet exist. 
      3. Inquiries are questions or discussion of the project.
      4. Schedule Items are things like meetings -- this category is generally not used at UWSC.
6. Assigned To
   1. Each area of a project (e.g., Instrument, Database, Etc) can have a different person responsible for the issues that arise in that area. If that person is specified in the project setup, FogBugz will assign the case to that person automatically when the Area is changed. Otherwise FogBugz will assign the case to the project's Primary Contact. 
   2. You can select a different person to assign the bug to if desired.
7. Status
   1. This box is greyed out when creating a new case because all cases start out as Active. 
   2. Other Statuses include different flavors of "Resolved" and "Closed."
   3. IMPORTANT: It is the responsibility of the person who submits a case to come back and close the case after verifying that the issue has been resolved. The submitter is the only one who can actually verify the issue is satisfactorily resolved. 
8. Notify More Users
   1. More users can be added to a case so that they receive e-mail notification of changes and updates regarding the case. Note that the person designated in "Assigned To" receives notification automatically.
9. Correspondent
   1. Not used at UWSC
10. Priority
    1. Used to designate the priority of the issue.  The lower the priority number, the more critical the issue. 
    2. Developers fix bugs by order of priority. 
11. Parent Case
    1. Designates a case as a "parent" of the case you are submitting, and the submission as a "sub-case" under the parent. You can enter the bug number in this box (if known) or a keyword from the title (and FogBugz will search and return options in a drop-down box). 
    2. This is generally not used at UWSC, but can be used if necessary.
12. Subcases
    1. Designates other cases as sub-cases of the submission (and the submission as a parent). 
    2. Selections are made as in 11.
13. Text Field
    1. Field for description of the issue. Be as specific as necessary to identify the problem and the proposed/desired resolution.
14. Due
    1. Can be used to specify a due date for the issue. This is generally not used at UWSC.
15. Estimate
    1. Not used at UWSC
16. Story Points
    1. Not used at UWSC
17. Kanban
    1. Not used at UWSC
18. Tags
    1. Not used at UWSC
19. Version
    1. Specify the version of the document/instrument your case is referring to. 
20. Computer & Caseid
    1. If using CASES, note the computer terminal and the caseID the submission is referring to. This assists with replicating the issue if the developer cannot identify it in any other way.

Notifications:

You will be notified of changes/updates to cases you submit, as well as any cases that are assigned to you. You can easily access those cases by clicking on the link supplied in the e-mail you get from FogBugz. You can customize your notification settings through your account in FogBugz.