Vote #63493
完了Issue loses custom field values
開始日:
2008/06/23
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
14
version_id:
2
issue_org_id:
1516
author_id:
291
assigned_to_id:
0
comments:
4
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
説明
An issue may lose all its custom field values.
Steps to reproduce:
create one required and one non-required issue custom field¶
create a tracker that uses these two custom fields¶
create a new issue using the tracker and enter values into both custom fields¶
when the issue is shown click on update¶
with (for example) "Firefox DOM Inspector" remove the required custom field from the DOM¶
submit the form¶
error message "<> can't be blank" appears (which is correct)¶
enter the ticket id in the search field to reload the page¶
Result:
the issue's custom fields are blank (and no journal details are written)¶
Expected Result:
the issue should not have changed¶
journals
I did a bit more testing and found out that you don't have to remove the required custom field from the DOM: just leave it empty.
--------------------------------------------------------------------------------
Confirmed. A fix should be committed soon.
--------------------------------------------------------------------------------
r1592 should fix this problem.
Now if you do not post custom field in your request, no change is made.
--------------------------------------------------------------------------------
Looks good!
Thanks!
--------------------------------------------------------------------------------
いいね!0