FogBugz Plugins are snap-in modules that customize your FogBugz site and add powerful new features. They can add new widgets and user interfaces, make FogBugz integrate with other systems, and perform custom tasks in response to a wide variety of events or actions.
Visit the FogBugz Plugin Gallery to browse the list of available Plugins. If you don't find the Plugin you're looking for, it's easy to develop your own if you have a bit of experience with C# (or another .NET language).
Developers interested in creating new FogBugz Plugins will find complete documentation, scores of helpful examples, and useful how-to guides on the FogBugz Developers Wiki.
FogBugz Plugins are .NET assemblies that run on the FogBugz server, and anyone with a little experience with C# shouldn't have too much trouble creating a useful Plugin. Using our powerful tool set you can add new user interfaces, run platform-independent database queries, create a custom data model, handle AJAX requests, modify styles, and much more.
These plugins give a taste of what's available.
Many more await in the FogBugz Plugin Gallery.
Out-of-the-box, FogBugz provides an intentionally simple workflow for case resolution and closure. We have four category types (Bug, Feature, Schedule Item, and Inquiry), each with a single "Active" status and a few different "Resolved" statuses. As a rule, cases are automatically assigned back to the case opener when they're marked "Resolved," so that the opener can judge whether the case can really be closed. We use this simple workflow at Fog Creek Software, but recognize that some customers would like to make a few tweaks to suit their unique work processes.
The Custom Workflow Plugin allows you to customize the set of case categories and statuses available on your FogBugz site, then specify how they behave in a workflow, which we formally define as a set of rules for case assignment based on case status. Any number of workflows can be created, and each FogBugz project can be assigned an individual workflow that matches the team's working style.
If the case fields provided by FogBugz don't quite serve your needs, you can use the Custom Fields Plugin to add a new one in a matter of minutes. The field can be any of several types including text, drop-down, and date/time.
Once the custom field is created, you'll be able to edit the new field in the case view, see a new column in the case list, and even filter results by possible field values.
The "Product Backlog" is central to Agile / Scrum project management practices. It's essentially a feature wish list sorted by order of implementation. (Sometimes items in the backlog are called "user stories;" feel free to use the Custom Workflow Plugin to call them anything you want!)
The Project Backlog Plugin allows you to manage a project-wide backlog without ever leaving the FogBugz case list. You can assign a case an order in the backlog just by clicking on the case's "Backlog" column and entering a value.
At the start of a new sprint, the project manager can choose which features at the top of the backlog will be implemented and assign them to a new milestone that represents the end date of the sprint. Once developers get started working on their assigned cases, the manager can view a continuously updated Burn Down Chart to make sure the sprint is on schedule.
Check out our Extras page for a list of clients, tools, and utilities that work with or extend FogBugz functionality.
You can now filter your case list for cases that were resolved between two tags in Kiln. This deeper connection between your case list and source code activity means better control over the release process, improved forensic knowledge of what happened in the past, and a totally new way to facilitate the communication between development and QA.
Even if you don't use the filter controls, you can see the same information for any individual case in the improved "Checkins" dialog.
As a developer, you're already overloaded with information. Emails, customer issues, bugs, documentation. FogBugz does an excellent job of allowing you to manage all of that information through the use of filters and notifications. Kiln extends FogBugz' workflow by implementing code reviews as FogBugz cases.
You can search and sort reviews from FogBugz, add them to your customized filters, subscribe to them for change notifications, and star them for later reference—just like you do right now with your cases. Because code reviews work with your existing FogBugz workflow, they're trivial to add to your routine—not a bolt-on afterthought like other systems.
Kiln leverages FogBugz's existing authentication system to make sure you have one less thing to remember. Log on once, to either FogBugz or Kiln, and you're all set.
This means that switching between FogBugz and Kiln is completely seamless for users. And administrators everywhere can rejoice that there is not yet another system to create accounts on when a new developer starts working.