Vote #68611
未完了Improve custom fields checks when changing any setting
ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Custom fields_14
対象バージョン:
-
開始日:
2010/11/15
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
14
version_id:
0
issue_org_id:
6894
author_id:
23347
assigned_to_id:
0
comments:
0
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
説明
Hi,
I think that some checks need to be done before a important change is done to a custom field. For instance, today I unset the "For all projects" of a custom field, and due to this change some queries which used this field failed (the classic Error 500). In my opinion, when such a change is done, Redmine should check first if the field is already used by some project and, if so, warn the user that the queries may fail, or even best, link the field to the projects that already are using the field.
Thanks.
いいね!0