Fog Creek Software
Discussion Board




"Fix for" bug in 3.1.9

When assigning a case the field "Fix for" lists unassignable releases and thus you can assign bugs to an unassignable release.

Morgan
Thursday, November 06, 2003

That's only the case when the bug you are editing is currently assigned to that fix-for.  If you change the fix-for, you want be able to assign it to the unassignable case again.

Is this a new case, or editing an existing case?

Michael H. Pryor
Thursday, November 06, 2003

I have set Assignable=No for "undecided" in Releases (all projects)  but are still able to create new cases and select "undecided".
I have done some more testing and it only affects Releases that are available for all projects.

Would a quick fix be to remove this row from the "FixFor" table in the database ?

Morgan
Friday, November 07, 2003

That's the same reason... A bug in its unknown state is assumed to be assigned to the undecided fix-for, so when you create a new bug, its "undecided" which is why undecided still shows up in the drop down ... (We ALWAYS allow the current state of the bug to be in the dropdown).

You can change ixFixFor in CBug.asp in Class_intialize to 0 and that won't happen anymore.

Michael H. Pryor
Friday, November 07, 2003

Tried your fixed, and it works.
Thanks !

Morgan
Monday, November 10, 2003

*  Recent Topics

*  Fog Creek Home