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

Send & Close Makes Case Unretrievable

When we use Send & Close (via "Email" or "Reply" on a Case), the Case is closed, this is good. However, we can no longer retrieve the Case in FogBugz, if we search the message returned is: Case #100515 does not exist or has been deleted. Case #100515 is an example number. Is this by design or a bug? Thanks.
Kerrie Senyk Send private email
Monday, January 9, 2006
 
 
Hi Kerrie,

The first thing I would do is install the latest version of FogBugz.  It sounds like there's a possibility that a code modification on your end is making cases unreadable.

By default, all Send & Close does is resolve the case as responded and close it.  It does not delete the case.
Michael H. Pryor Send private email
Monday, January 9, 2006
 
 
Hi, Michael, thanks for your response. We haven't made any code modifications to our FogBugz installation. Currently, we are on 4.0.31. Please see if you can reproduce the issue. The steps are:
1. Take an Active Case.
2. Click the Reply (or Email) button.
3. Type a response.
4. Click Send & Close.
After that (on our system), the Case is no longer retrievable via Search or Filter. One thing we did notice in the database (SQL Server 2000), in the BugEvent table, the "sVerb" column has a NULL value for the Cases that we have used Send & Close. All other Closed cases have some value in the sVerb column for every row in BugEvent. I hope that helps clarify the issue. Thanks again.
Kerrie Senyk Send private email
Monday, January 9, 2006
 
 
Hi Kerrie,

Please run the upgrade to reset FogBugz.  I think it should fix your problem.

-Michael
Michael H. Pryor 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.