id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 12252 Incorrect initialization of new custom fields in existing tickets. roger.oberholtzer@… Ryan J Ollos "When adding a custom field, it is possible to set what the default value should be when a new ticket is created, For existing tickets that do not yet have this value, the field seems to default to the first value (I have a 'select'-type variable). I would have expected it to be set to the same default value as for a new ticket. Is this expected behavior? I really would like all existing tickets to have the default value for this field. It has been confirmed that this same behavior exists in the current trunk release." defect closed normal 1.2 ticket system 1.0.2 normal fixed Tickets created before a custom field was added default to using the default value provided in the custom field definition.