Upgrading to FogBUGZ 3.0? The new version contains 50 major improvements which will help you work more productively and use FogBUGZ in new ways.
Separate Bugs, Features, and Inquiries. Use FogBUGZ to keep track of new development tasks. If you’re doing Extreme Programming, FogBUGZ is ideal for keeping a sorted list of prioritized user stories. Use inquiries to keep questions and potential bugs separate from confirmed bugs.
Subscribe to any bug to get email notifications when it changes.
Duplicate tracking creates a link between duplicate bugs.
Inline pictures for screenshots, etc.:
Outside customers can submit bugs without logging on. This feature can be turned on and off on a per-project basis.
Email into FogBUGZ. With the new Mailboxes feature, FogBUGZ can read email sent to any account (requires a POP3 mail server) and convert each email message into a FogBUGZ case. Use all of FogBUGZ’s great tracking features to handle customer service email. You can also set up mailboxes for bug reports, feature suggestions, etc.
Reply to /Forward emails from FogBUGZ. Once an email message has been received in FogBUGZ, you can assign it and track it just like any other case. You can also reply to the email or forward it from FogBUGZ itself. FogBUGZ inserts the case number in the subject line so if your correspondent replies, their reply is appended to the same case. This keeps a complete record of the email interaction, even when several people work on it.
Cleaner UI looks better, requires fewer clicks for common actions, and virtually eliminates the need to scroll to the bottom of a page.
Bug edit box appears at the top so you don’t have to scroll to the bottom to add a comment to a bug.
Grid mode for lists fits more information on one screen:
Closing a bug automatically takes you back to the list screen.
Next/Previous buttons make it easy to work through a list of bugs without going back to the list every time.
No self-notification. To avoid mailbox clutter, you no longer get an email notification telling you about something you just did.
Email notifications on edit. If someone else edits a bug that is assigned to you, you get a notification.
Change the bunny pictures as easily as dropping new pictures into a folder. Some people prefer to have distinguished portraits of the executives at their company rather than our signature cute furry animals.
Bulk Assign, Resolve, Close, Reactivate, or Reopen a bunch of bugs at once from the list screen.
Standards-compliant XHTML source code supports the latest web browsers and degrades gracefully on old web browsers.
Searching in full text also searches titles. (About time!)
Vastly improved SETUP does everything you need to get FogBUGZ up and running in a matter of minutes:
Contact form automatically sends email to all local administrators.
Automatic license tracking.
Import licenses from the Fog Creek online store in one step.
All reports include hyperlinks so you can quickly drill down.
Filter for bugs with a priority less than or greater than x, for example, you can see all bugs with priority 3 or higher.
Filter bugs based on when they were resolved or closed, for example, you can get a list of bugs closed today.
More ranges for time-filters, for example, list bugs opened in the last year.
Filter bugs with ANY resolution to find bugs that are resolved but not closed.
Crashes in FogBUGZ can be sent to Fog Creek Software with one click. Not that it will ever happen. But if it does, we have a magnificent track record of fixing things quickly.
More documentation and improved online support.
Localizable UI with all strings in one place for easy translation. FogBUGZ is also fully unicode-compliant and supports text in virtually any language or alphabet.
Typing “bug nn” anywhere in a bug report automatically becomes a link to that bug.
The project and area are remembered when you create a bug and appear as the default for the next new bug.
Time stamps on bug events let you see exactly when something happened.
“Back” works in browsers more often, for example, when you are viewing a bug you can click back to go back to the list page without getting a “page expired” message.
BugzScout lets you capture crashes in your products and report bugs over the Internet automatically. FogBUGZ checks for duplicate crash reports and merges them automatically, and can then send a custom message back to the user based on the exact crash. For Windows applications, we supply an ActiveX control (available from the Fog Creek Software web site) that enters bugs in FogBUGZ. For virtually any other programming environment, use any HTTP library to submit bugs and get results in XML.
Support for the latest standards-compliant browsers like Mozilla.
Improved mail-sending code works with more SMTP servers.
Support for Perforce as well as CVS for source control integration.
Simpler URLs for bugs. If your server is bugz.example.com, you can link to bug 123 with the URL bugz.example.com?123.
Bug commands (assign, resolve, etc.) are duplicated at the top of the screen so you don’t have to scroll.
Text area for bug reports grows automatically so you don’t have to scroll.
Beginner tips appear neatly in the right margin, and, of course, you can still turn them off.
Support for SQL Server even if you don’t have SQL server full-text search installed.
Filter on bugs without estimates makes it easier to use FogBUGZ for scheduling.
Better browser detection.
Easier site configuration. Some of the things that we used to ask for are now figured out automatically. Other things that we asked for in two places are now in one place.
Fast, OLEDB database connection instead of ODBC.