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

FB6: Another UI Beef: Order of fields when creating New case

Continuing the discussion started:



When creating a new case, the Estimate edit is before the Version edit (our first custom field is Version).

When creating new cases, we almost ALWAYS enter the version (just the build #, actually, e.g. .1234), but we never enter estimates when creating cases.

I seem to remember a Joel article mentioning:

--It should be easy to enter cases
--QA and project management should not dictate schedules to the devs

Perhaps I misremember?

In any event, I find the FB6 layout to be simply out of sync with how we work, and with how FB4 and FB5 were laid out. We need Priority and Version up there in the top block, as part of the simple tab order. As it stands, we essentially have to use the mouse to create cases, as the overall layout and tab order is simply out of whack.
Sam Jones
Monday, December 3, 2007
I've added these comments to the case I created for the other post.  Thanks!
Michael H. Pryor Send private email
Tuesday, December 4, 2007
FWIW we are the other way around.

We almost NEVER put anything in the two User Defined fields, whereas we almost ALWAYS put an initial estimate of time in.

(For us Version-specific-attributes for Cases are not relevant - single web-based product, weekly rollouts to live) so we have reused both fields for other tracking info which is not often required)
Krispy Send private email
Wednesday, December 5, 2007
Other problems with the UI from FB6 that I run into on a daily basis (I'm not sure if they have been mentioned already):

- The Correspondent name has a hard break after the @ sign.  Even for very short names like show up as


Putting this on a single line above the case instead of wrapping it would be much nicer.

- Hiding checkins related to a bug way down the side, and then behind a popup!  This is probably the #1 or #2 item I want to know about a bug when I go to look at it.  It took us over a month to realize that the script to link checkins to bugs was not actually broken by the upgrade to 6.0.

- Long lines, if they are not wrapped due to a lack of spaces, are actually _cut off_ by the stylesheet.  It's necessary to toggle stylesheets off to actually get at this information.

FYI: one of our primary uses of FogBugz is for phone-home reporting of application crashes, so typically post mortem information like stack traces is in the bug information.  FB6 handles this extremely poorly due to the combination of limited horizontal width and large font size.  For column data it typically wraps around column 55-65.  We see this as well in the bug titles - put the literal EXCEPTION_ACCESS_VIOLATION in a bug title and see how it gets nearly an entire line to itself.
Benjamin Carter
Friday, December 7, 2007
Suggestion: allow a stylesheet directive in the Crash Report that converts to <pre> or somesuch, so that the crash reporting can force a style within FB.
Krispy Send private email
Sunday, December 9, 2007

Thanks for the feedback.  We're aware of this width overflow issue and keeping our eyes on possible fixes.  In the meantime, here are some bug view width customization tips which may help you: .
Ben Kamens Send private email
Monday, December 10, 2007
Also, if anybody has any success w/ Krispy's technique, let us know!
Ben Kamens Send private email
Monday, December 10, 2007

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.