Actions
Defect #2220
openNew Custom Fields not propagated to old issues
Status:
New
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2008-11-21
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
Description
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.
Actions