Making Project Management Work -- The FogBugz Philosophy -- Lifecycle of a FogBugz Case -- Managing Cases -- The Three Types of Cases -- Where Do Cases Come From?- Entered via Web Interface (local/customer) -- Entered via e-mail -- BugzScout -- Screenshots and attached files -- Filtering cases -- Being a Good FogBugz Citizen -- How devs/qa/mgt should work with FB -- Making FogBugz work for you -- Setting up Users and Groups -- Setting up Projects etc -- Setting up Permissions -- All the other lists you can change -- Getting the Big Picture -- Tracking estimates -- Using Due Dates -- Resolving cases -- Creating Release Notes -- Reporting/Extending -- Working with E-mail, RSS, and Discussion Groups -- E-mail -- Subscribing -- Customer e-mail -- RSS -- Discussion Groups -- Working with Source Code Control -- Setting up SCC -- Getting from Cases to Code and vice versa -- Appendix A: Setting up FogBugz -- Installing on Windows -- Installing on Unix -- Installing on MacOSX -- Customizing FogBugz -- Overall -- User options -- Appendix: BugzScout sample code.Many programs purport to help a development team manage a project but most of them aren’t very good. Enter FogBugz. This dynamic tool is based on keeping track of a database of cases. At any given time, cases are assigned to one person, who must resolve or forward them to someone else. With FogBugz, cases can be prioritized, documented, sorted, discussed, edited, assigned, estimated, searched, and tracked. And because FogBugz is web-based, everyone on a development team has access to the whole picture, at any given moment. That picture may include everything from customer feature requests, to high-level design discussions, to tiny bug fix details. This book (written under the guidance of the entire FogBugz team) completely describes the ins and outs of the latest version of FogBugz.