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

Who was the case assigned to?!!

I just noticed something strange today, when trying to find the number of CLOSED cases per user in FogBug.
Could someone please tell me, why in the name of all that's holy does FogBugz "forget" who a case was assigned to after it is closed?
In the Bug table, the owner is changed to "CLOSED" (sic!).
Is this information retained anywhere else? Is there anyway to find out who had worked on a given case?
me
Monday, December 19, 2005
 
 
Saying that the FogBugz "forgets" who the case was assigned to when closed is kind of the wrong way to look at it.

It's right that the case isn't assigned to anyone any more.

In the FogBugz model no-one "owns" a case. A case can be worked on by a bunch of different users at different points in its lifecycle. At the time it's closed, there's no-one working on it.

You can browse back through a case's history to see who has done what at various points in its journey from creation to closure.
Andrew Lighten Send private email
Monday, December 19, 2005
 
 
Can'I measure the time each person work in a group of Cases ?
Julio Cesar Send private email
Monday, December 19, 2005
 
 
In that case, can I find out who was the last person to work on a given case?
me
Tuesday, December 20, 2005
 
 
You can either do it by going to that case and looking in the history, or you can hit the database directly.

For example, suppose you wanted a report of who closed which cases and when. You can run the following SQL script to get that information:

----------------------------
select be.ixBug, b.sTitle, p.sFullName, be.dt from Bug b, BugEvent be, Person p where be.ixPerson=p.ixPerson and be.ixBug=b.ixBug and be.sVerb='Closed' and fOpen=0;
----------------------------

If you want to know a specific case number, simply add "and b.ixBug = nnn" to the end of the sql statement, where nnn is the bug number.

Cheers
Bryan Send private email
Monday, January 9, 2006
 
 

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.