FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Some comments of FogBugz 6

Some observations from playing around with the trial.

Firstly, well done on the new look, really like it (with one exception, see below). It fixes up the problems with the old look (am thinking about the title box) without requiring users to relearn FogBugz.

Having said that, what's up with the case number when viewing the case? It's huge! Why? It never seemed a problem before, and now it's overpowering.

I love being able to quickly type cases into the list view to add them, but it would also be nice to be able to edit other properties from the list view (assigned to, estimates...). Maybe I'm missing how to do this.

EBS is great if you have all your bugs/features in FogBugz, but it can't account for bugs that you've yet to find. So when developing a feature, even though the feature may take 2 weeks, if your testers find bugs and add them, it will push out the estimate of the project longer, even though the 2 week estimate already had taken into account fixing bugs. So what should we do here? Estimate how long the feature will take excluding bug fixes, and accept that the initial estimate will be off, or add the bugs as notes on the original feature case?

It's still missing my "most wanted feature" the ability to pick who opened this case. I've heard a lot of other people requesting this as well.

I love the virtual users. Good thinking.

What's up with the lack of fanfare? I was expecting an e-mail to all current customers. Especially customers with support contracts. I realise you have the world tour, but relatively few people will see that.

Finally what with with the Kiwi? You're picking a country's mascot for the icon for your program? Can "Kiwis" at least get a discount? :p
Ray Send private email
Thursday, September 6, 2007
 
 
One more thing, that I actually assumed you had implemented, since it has been requested so much.

I still can't select multiple values for filters.
E.g. Show me the cases assigned to DevA or DevB.
Ray Send private email
Thursday, September 6, 2007
 
 
"to be able to edit other properties from the list view (assigned to, estimates...)"

Sure, just double click the estimates area in the list view and an edit box will pop up.  This doesn't work for assigned to though, just estimates.

"EBS is great if you have all your bugs/features in FogBugz, but it can't account for bugs that you've yet to find."

That's what schedule items are for.  You would enter things like "debugging", "buffer" etc as schedule items and then you can charge your time to those later (using the working on menu item).

"What's up with the lack of fanfare?"

It's called a "soft launch". In other words we wanted to let a few people try it and work out the kinks, update the web site, etc and then make the big announcement.  It's coming though very shortly.

"I still can't select multiple values for filters.
E.g. Show me the cases assigned to DevA or DevB"

You can do this!  You have to check out the amazing new search features (which can be saved as filters).  They rock.  Just search for "project:blah status:active (assignedto:deva or assignedto:devb)" and then save that as a filter.
Michael H. Pryor Send private email
Thursday, September 6, 2007
 
 
Regarding "Schedule Items"...

I really like the idea of them but I am curious about how best to use this class of cases to maximize the effectivness of EBS.

Give a hypothetical project that estimates out to 4 weeks of developer time, I also want to include an equal amount of time for debugging.

This project has two developers and two qa engineers. When talking about feature cases it is easy to assume that only one developer will be assigned a case so EBS should work just fine...

When I create a single "debugging" schedule item how do I accomodate two QA engineers? Should I create two debugging schedule items, one for each qa engineer?

Thanks for the help.
Brett Clapham Send private email
Tuesday, September 18, 2007
 
 
All items have to be assigned to a person, so you would create two schedule items for each QA person...

but the problem is that if you looked at the chart, since the QA people don't have anything assigned to them currently, EBS would assume they could start working on Debugging now, and would tell you that these two people will be done in two weeks.

This is something we have to think more about...
Michael H. Pryor Send private email
Tuesday, September 18, 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.