Defect #2220

New Custom Fields not propagated to old issues

Added by gabriel scolan about 14 years ago. Updated over 11 years ago.

Status:NewStart date:2008-11-21
Priority:NormalDue date:
Assignee:-% Done:


Category:Custom fields
Target version:-
Resolution: Affected version:


It seems that when you define new custom fields for an issue, no value (default value would be expected) is set to the issues previously recorded.
Looking at the records in the database, the table custom_values do not contain the new custom field on old issues (customized_id)
I'm on the 0.8 trunk.


#1 Updated by Jean-Baptiste Barth over 12 years ago

Confirmed, but it may be a good thing, it depends on how you use custom fields. In some cases I just don't want previous issues to be updated with the new default value. Can you think of a simple way we could handle both situations ?

#2 Updated by Toshi MARUYAMA over 11 years ago

  • Category set to Custom fields

Also available in: Atom PDF