|
|
sir thraxisp, please try this:
- make a custom field with date type.
- edit the custom field properties. check "display when updating issues" and "display when reporting issues". DO NOT check "required on update".
- attach custom field to a project.
- report an sample issue. input a date into the custom date field. submit.
- view the issue normally. take note that the custom date field has your value. now, assign the issue using the assign button. you will be directed to the bug_change_status_page.php. note that the custom field is not displayed.
- choose someone to assign to, submit.
- view the issue again normally. take note that the custom date field is now empty. the bug history also records that it has been set to blank.
**** some personal notes:
i think the problem is, since the bug_change_status_page.php does not display the custom date field, the gpc_get_custom_field() in bug_update.php returns an empty string (as opposed to nulls for other field types). since it is not null, it will pass through the custom field validations in bug_update.php into custom_field_get_field(), where the data will be reset to an empty string.
if the date field will be displayed even if it is not required on the bug_change_status_page.php, i think the process will be ok. |
