Vote #64176
未完了New Custom Fields not propagated to old issues
ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Custom fields_14
対象バージョン:
-
開始日:
2008/11/21
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
14
version_id:
0
issue_org_id:
2220
author_id:
1031
assigned_to_id:
0
comments:
2
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
説明
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.
journals
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 ?
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
いいね!0