Creating and Editing Areas

Within each project, you can divide cases into areas. The primary use of areas is to let people find the cases that they'd like to work with by creating filters for a particular area. For example, you might have separate areas for the code and the documentation of your project.

In general, you'll find that the fewer areas you have, the more likely people are to categorize cases correctly into the right area. Think of it this way: if you have 100 areas, everybody who enters a case is going to have to consider each of those 100 areas to decide which area is the best fit. Inevitably, cases will be miscategorized, and the pain of choosing an area may even make people enter fewer cases. If it's easier to jot down a case than enter it into FogBugz, you're going to lose the benefit of bug tracking.

When you first create a project, FogBugz creates a default area for that project named Misc. To create a new area, click the Create New Area link on the project's editing screen. This will open a screen that prompts you for the single piece of information required to define an area: the area's name. Enter a name, click OK, and FogBugz will create the area.

■Tip FogBugz automatically creates special areas to handle spam and unsorted mail in e-mail-enabled projects. You'll be able to identify these areas by notes on the listing of areas. You can't add notes to your own custom areas through the FogBugz user interface.

You can also edit and delete areas from the project editing screen. If you delete an area, cases that were previously assigned to that area remain assigned to that area, but you cannot assign new cases to that area.

For many projects, you'll be able to identify a small set of areas, each of which belongs to a different user. For example, you might end up with Documentation, Setup, and Core as your areas, as well as the default catch-all Misc area. Set up these few areas when you first create the project, and use them to categorize the initial cases as they come in. Then add areas only after careful consideration and only if they are needed for a particular filter that you want to create. For example, if you have a developer concentrating on the Web interface, and they need to see all the bugs related to the Web interface, create an area named Web UI. Don't create more areas than you need for filters, because the more you have, the more likely cases will be misfiled.

0 0

Post a comment