Take a Tour of a FogBugz Case

Let us give you a tour of a FogBugz case. As you hover over different features, you'll see a brief overview of what the feature does. If you click, you'll get some more information as well as links to related resources.

Got it!

Still have questions? We're here to help.

FogBugz automatically generates RSS Feeds for cases, filters, wikis, and discusion groups. Use your choice of RSS aggregator to receive notifications about changes.

RSS Feeds: Stay on top of your cases with by using our automatically generated RSS feed. (Click for more info!)

In FogBugz, a case is always assigned to one and only one user. This is a core FogBugz principle: a case owned by more than one person is owned by no one. This prevents your cases from slipping through the cracks. You can customize your workflow by assigning cases to virtual users or handling case assignment through our API.

Case Assignment: Each case is assigned to one - and only one - user until it is closed to help make sure that none of your cases slip through the cracks! (Click for more info!)

FogBugz subcases allow you to break down a feature into a set of subfeatures, or, more generally, break down a task into smaller subtasks. At Fog Creek Software, our adds incoming support inbox cases to cases for new features to track customer interest in new features and aggregate customer feedback on recent releases.

Pro-Tip:Type a new case name into the "Subcases" field to create a new subcase on the fly!

Case Hierarchy: Use subcases to break down a feature into a set of subfeatures, or, more generally, break down a task into smaller subtasks. (Click for more info!)

Every FogBugz case on your account has a unique case number. You can use the case number to search for the case, link the case to others as parent cases, subcases, or related cases, or access and edit the case through the FogBugz API. Clicking the case number will refesh the case (you'll also see a message at the top of the screen if a change is made to the case while you are working on it). Additionally, email correspondence is linked to a case by the case number in the subject line so that all emails on a single thread stay in one case.

Case Number: Each case has a unique id which you can use to search for the case or link it to another as a parent, sub-case, or related case. (Click for more info!)

Categorize your cases for easy filtering. FogBugz ships with four categories, Bugs, Features, Inquiries, and Schedule Items, but you can add custom categories to meet the needs of your team's workflow. You can also add your own icons for each custom category!

Category: Sort your cases into customizable categories for easy filtering. (Click for more info!)

On cases generated by incoming email pulled into a FogBugz mailbox, the correspondent is the email address of the customer who sent the email. (This example case does not have a correspondent because it is not an email case.) Correspondents will receive email replies to a case but will not received notifications for other case edits, so it is safe to use case edits to communicate with your team about an email case.

Correspondent: The external customer whose incoming email generated this FogBugz case. (Click for more info!)

Custom fields allow you to track attributes of cases beyond the standard attributes (Project, Area, Milestone, etc) that ship with FogBugz. In this case the team is using a Custom Field to track a client code for billing purposes. Custom fields can be set on a per project basis, and can be placed in either the case header or the sidebar.

Custom Fields: Add custom fields to your case views to track additional data about cases. Custom fields can be added either up here or in the sidebar. (Click for more info!)

Keep track of your cases by setting due dates. Once you done this, you can sort cases your list view by due date. You can also save a filter so you can easily access all of your cases that are due today or tomorrow. Due date is also one of the factors that is considered as part of "importance" for our "orderBy:importance" filter.

If you are using FogBugz as a help deslk, you may also find it helpful to automatically set a due date for each case generated through incoming email.

Due Date: Make it easier to keep track of your cases with setting due dates. (Click for more info!)

Often, we're asked before we start a project how long the project will take to complete. Almost as often, our estimates are wrong. Evidence Based Scheduling keeps track of the historical accuracy of your estimates to give you a better idea of how far you are from the finish line.

To take advantage of Evidence Based Scheduling, you and your teammates will need to make estimates for all of your cases, and you'll need to use time tracking to keep track of how much time you're actually putting in on each case. We compare the amount of time you thought it would take you to complete a case to the amount of time it actually took you, and we build a history of your accuracy. In time, we'll be able to see your estimates and use the data we have to make our own estimate.

While we recommend that developers make their own estimates, we'll keep track of how well you estimate the time it will take others as well. Importantly, Evidence Based Scheduling is based on the historical accuracy of the estimator, not the historical speed of the developer assigned to the case.

Evidence Based Scheduling tracks the accuracy of your estimates over time to help you gauge when your team will finish your sprint. (Click for more info!)

FogBugz integrates seamlessly with Kiln, Fog Creek's version control software. Simply include a case number in a commit message to have a link to the committed changeset appear automatically in the case along with the commit message.

Kiln Changesets: Kiln users can link code changesets directly to a case by including the case number in the commit message. (Click for more info!)

FogBugz integrates seamlessly with Kiln, Fog Creek's version control software. Simply include a case number in a code review description to have a link to the code review appear automatically in the case sidebar.

Kiln Code Reviews: Kiln users can link code reviews directly to a case by including the case number the code review description. (Click for more info!)

If you're running an agile team, you can think of milestones as sprints. Organizing your cases into milestones is the easiest way to keep track of a group of cases scheduled for a particular deploy. Using our Iteration Planner, you can easily view your cases organized into milestones and transfer them between milestones. Using milestones will also allow you to take advantage of our Evidence Based Scheduling and Time Tracking module, which will help you estimate your time until your next deploy.

Milestones: Milestones are a way for you to organize incoming cases into sprints, deploys, or builds. (Click for more info!)

Sometimes, you'll want to let a teammate know that you've made a change to a case without assigning the case to them or subscribing them to the case. When that comes up, "Notify more users" is your best option.

Notify More Users: Use this feature to send a notification to one or more of your teammates when you make a change to the case. (Click for more info!)

Priority is one of a number of ways to indicate the importance of a case to your team. Using the priority feature will allow you to order cases by priority in your list view or create filters so that you can see only your high priority features. Priority is also one of the factors that is considered as part of "importance" for our "orderBy:importance" filter.

Priority: Priority is one of a number of ways to indicate the importance of a case to your team. (Click for more info!)

Projects are the top level of FogBugz categorization. They're ongoing areas of effort (not necessarily a project you would do for a customer). 'FogBugz' is a project in the Fog Creek install for example.

Areas are the organizational unit underneath a project. This can be a part of your application, or a functional division (Documentation, Testing, Deployment).

Projects and Areas: Divide your work into projects and areas to manage permissions, stay organized, and run an agile team. (Click for more info!)

Choose between a plain or rich text editor when you are making case edits. Click to edit your cases in HTML.

Combined with our XML API, virtual users can be a powerful tool. For example, you can use our XML API to randomly assign cases to your members of your team. In addition, virtual users can be passed into API calls as ixPerson if you want to automate aspects of your workflow without having your own name attached to each change.

Rich Text Editor: Use the rich text editor to format your text or add HTML to your case edits. (Click for more info!)

Including word case followed by any case number (e.g., "Case 1485") will create a link to the case, add it to the list of "See also" cases in the sidebar, and add your current case to the linked case's "See also" list.

See Also: Link two cases by including the text "Case [case-number]" in any case edit and each case will appear in the other's "See also" list. (Click for more info!)

The status dropdown is a simple but powerful FogBugz attribute. Leave a case active to keep it on your radar in your "My Cases" filter. Resolve (Waiting For Info) to postpone it to a later date or until another case is resolved.

How you resolve a case also has an impact on Evidence Based Scheduling. If you mark a case as "Resolved (Fixed)", the original estimate for the case will factor into the estimator's historical record. If you mark a case as "Resolved (Won't Fix)", that estimate won't count toward the estimator's record moving forward.

Status: By setting the status of your FogBugz case, you can postpone it until a later date, merge it with another case, or let it fall off your radar. (Click for more info!)

Story points are a way of providing estimates for features. Use them in conjunction with our Iterarion Planner to run your scrum team.

Story Points: An alternative to time estimates for agile development without our Evidence Based Scheduling module. (Click for more info!)

Subscribe to a case to receive a notification for each change to a case. Within the case view, you can manually subscribe by clicking "Subscribe" in the sidebar. You can also use "Add Subscribers" to subscribe your teammmates. Use our autosubscribe feature from the case list view to automatically subscribe to all cases in a project or area.

Subscriptions: Subscribe to a case to receive a notification for each change to a case. Use "Add Subscribers" to subscribe your teammmates. (Click for more info!)

FogBugz has a ton of built-in categorization options, but if you need an ad hoc way to group cases and wiki articles together, use tags. Tags are lightweight in that you don’t need to pre-configure anything (e.g. set up a new custom field) but you can still search and set up filters based on tags.

Tags: Tags are a quick and easy way to group cases and wikis together. (Click for more info!)

Virtual Users are free users you can use to queue cases for assignment. In this case, for example, Evelyn has assigned the case to an "Up For Grabs" virtual user so that anyone in her pool of testers can take the case when they're free.

Combined with our XML API, virtual users can be a powerful tool. For example, you can use our XML API to randomly assign cases to your members of your team. In addition, virtual users can be passed into API calls as ixPerson if you want to automate aspects of your workflow without having your own name attached to each change.

Virtual Users: Free users you can create for the purpose of queuing cases for assignment or updating cases through our API. (Click for more info!)