The 'undecided' fix for is still assignable, even though I've marked it as not assignable. How so?
Wednesday, October 01, 2003
This is intentional.
In 3.1.9 all cases that have properties that are no longer assignable will still show those properties when you edit a case. This is so when you edit an old case that has an unassignable fix-for, it doesn't change the fix-for to something new.
A new case has no fix-for, as its fix-for is undecided. So even if you set it to unassignable, new cases will always have undecided in the dropdown.
You can change this in CBug.asp by changing ixfixfor in Class_intialize to 0.
Michael H. Pryor
Friday, October 03, 2003
If you want you can also set the "Fix For" drop down to be the current project you are working - so it will come up by default and people won't have to change it all. (unless it belongs in a different release
Get the "IxFixFor" for your current release out of the FixFor table in the database.
Then do as Michael suggested and change CBug.asp by changing ixfixfor to that number in Class_intialize.
(It was line 63 in my CBug.asp File)
Thursday, August 05, 2004
Fog Creek Home