[rt-users] RT 3.4.2 custom fields defaulting to value '1'

[David Glasser]

On Aug 2, 2005, at 3:07 PM, Jason Parsons wrote:


> After upgrading RT from 3.4.1 to 3.4.2, I'm finding that "enter one  
> value" and "select one value" custom fields are defaulting to a  
> value of '1' (instead of empty).  For example, I have a "select one  
> value" transaction custom-field called 'severity', with values:  
> 'normal', 'urgent', or '(no value)'.  When '(no value)' is  
> selected, and the transaction is saved, the transaction displays  
> with a severity of '1' (which is obviously bogus).
>

This bug should be fixed in the forthcoming RT 3.4.3.  Try 3.4.3  
release candidate 2 and let us know if this bug still exists.

--dave
   Code Monkey, Best Practical Solutions
-- 
David Glasser | glasser at bestpractical.com