Fog Creek Software
Discussion Board

Server error when using "unassignable" version

I'm evaluating your software for our company (Interactive Edge) and here is a problem I found, which I think is a major one:

Environment: Internet Explorer 6.0 build 6.0.2600.0000

Steps to reproduce:
1. Log on with Admin account
2. Create a new project
3. Add a release version to the project (does not matter if it is strictly for this project or for all the projects)
4. Create a new bug and select the release version in the "Fix For" field.
5. Go back to the "Project" management
6. Set the release version to unassignable
7. Go back to the newly filed bug
8. Click "Resolve"
9. Type any resolution text
10. Press OK

Observed behavior:
The application crashes with this error:
"FogBUGZ Internal Error
An internal error occurred in FogBUGZ. Please report this error to Fog Creek Software by clicking "Submit." 

File:  /default.asp 
Line:  841 
Error:  Connection object cannot be explicitly closed while in a transaction. 
Browser:  Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; .NET CLR 1.0.3705) 
Number:  0x800A0CAE 
Category:  ADODB.Connection 
Column:  -1 
QueryString:  pre=preSubmitBug 
URL:  /default.asp 
Content Type:  multipart/form-data; boundary=---------------------------7d33b01a3902b8 
Content Length:  968 
Local Addr: 
Remote Addr: 
Time:  3/11/2003 6:00:12 PM 

Expected behavior:
The bug should be set to the new "resolved" state with no crash.

I hope you can fix this bug , because we need to set versions to the "unassignable" state and be able to edit and resolve bugs linked to them.

Hope to hear from you soon.

Vassil Kovatchev
Interactive Edge, Inc
Director, R&D Programming
212.462.4900 x397
212.462.4911 (fax)

Vassil Kovatchev
Tuesday, March 11, 2003

Very strange.  I cannot reproduce the error you are seeing using your repro steps.  Were you able to reproduce it a second time?  Is this on the trial server?  Perhaps we could do a remote debug session when you get a chance and you could show the error to me...

Michael H. Pryor
Tuesday, March 11, 2003

Hi Vassil,

  It seems to be the same problem I had two weeks ago. We have tried to debug this problem, but we were unsuccesful. All the did to make it work again was reinstalling IIS and FB.

  Hope this helps.


Alexandre B. Corrêa
Wednesday, March 12, 2003

This is due to the fact that the case is being resolved and there are NO fix-fors.  (So the fix-for dropdown is actually empty).  I'll add some error checking to prevent this from happening.  This won't happen in normal usage scenarios because most people have a global fix-for called Undecided which is never not assignable.

Michael H. Pryor
Wednesday, March 12, 2003

*  Recent Topics

*  Fog Creek Home