id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 4061,existing tickets should get the default value if value is not set in ticket,GreenZero,Remy Blank,"actual situation: * creating a new ticket, severity will be set to the configured default severity * existing tickets with no severity set will get the first severity in configured order on modify after creating severities [[br]] required situation: * creating a new ticket, severity will be set to the configured default severity (already implemented = OK) * modify an existing ticket will set severity to configured default severity, too [[br]] this occurs after using trac in project where no severity was used at the begining. Later on severity was filled. Modifiing existing tickets causes them to be automatically set to highest priority if user did not pay attention to that ticket field and set it manually. It would be very nice, if you could fix this. ",defect,closed,normal,0.11.2,ticket system,0.10,major,fixed,ticket modify severity default custom field verify patch,oliver@… p.phaneuf@…,,,,