FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

Feature wishlist

After testing and comparing FogBugz for a few days, I can say that I am very impressed. Particularly with email handling. But I did notice a few issues that I'd like to see in future releases (some of which I've send to FogBugz already):

-The "case N" link feature is somewhat limited. I like that it creates a clear "Related Cases" field in the target case, but in the case that contains "case N" I have to go searching for the relate case. For every case, I would like to quickly see all of the related cases on both ends, not go hunting for links in comments.

-I would like to have more sophisticated relationships, like blocking dependencies. This would help with sorting. For example I may have a Pri 1 bug that is blocked by a bug that is (incorrectly) marked Pri 3. It would be nice to sort by dependencies and see this clearly.

-Why can't I reference {ticketurl} and other macros in normal (non autoreply) email? This would partially solve the current difficulty in retrieving lost ticket numbers.

-Global and personal email signatures would be a big help. These should also support {ticketurl} style macros.

-I'd like to be able to add columns to the grid view. I have a nice wide monitors, information that I would like to see, and a bunch of empty space. Let me fill it :)

-I'd like to be able to select from a list of predefined versions in the "version" field. Ideally I could select from a predefined list of versions and then be able to edit it. This could be handled with something like snippets, or maybe a popup window like filters.

-Machine config would also benefit from predefined lists or snippets. I don't want to type "WinXP Pro SP2, 512MB, etc. etc" over an over again.

-Roles: I'd like to be able to control permissions on a more fine grained level. Roles that come to mind that might have different permissions include (developer, testers, admin, client, reporter). For example "clients" could create and comment on cases, but not resolve them. Or they could be prevented from sending email.

We are planning to do a bit more evaluation, but FogBugz is currently the leading contender. Any feedback is appreciated.

Brad Schick Send private email
Wednesday, March 2, 2005
Hi Brad!

Thanks for the excellent feedback. We'll take it all into account for 5.0.

In the meantime :

For global and personal email signatures, you have two options -- define snippets (I have mine set up so that sig` is replaced with my signature block) or set up a "Message Template" in your mailbox. The message template field does allow the {macro} substitutions and is automatically inserted in any outgoing reply.

Thanks again!
Joel Spolsky Send private email
Wednesday, March 2, 2005
Thanks, that is a decent workaround. But I noticed that the template only applies to replies. Most email will probably be replies, but for those that are not the template is no help.

Snippets would work for signatures in that case, but it currently seems impossible to get {ticketurl} or other macros into non reply emails.

Brad Schick Send private email
Thursday, March 3, 2005
I'm going to second Brad's "wide monitors" feedback, with an added note about List View.

When viewing bugs in List View, the table is restricted to a fixed 750px width.  These 750px have to hold both the navigational tiles on the left (fixed at 200px), leaving only 525px for the actual list (again, fixed).

This causes bugs with longer than, say, 70 characters to wrap.  That reduces readability / scan-ability.

There is an ocean of available whitespace to the right of the list.  It doesn't seem to make sense to fix the list view to accomodate 800x600, esp. as the grid view doesn't fit very well in that width anyway....
John Hart Send private email
Thursday, March 10, 2005

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.