| Description | When you update or resolve an issue that has custom fields, but those custom fields are not displayed on the resolve/close page, the custom field data is set to blank.
Steps:
- Setup a custom field with all display and required flags off
- Assign the field to a project
- Raise an issue and enter data in the custom field
- Resolve (or close) the issue (you should not see the custom field on these screens, because it was switched off in custom field set up)
- The custom field will now be set to blank. The field is blank, and the change is also listed in the issue history.
(See below for a sample of SQL taken when resolving the issue.)
This problem definately occurs on the resolve and close pages but not sure it if happens elsewhere. |
|---|
| Additional Information | SELECT field_id FROM mantis_custom_field_project_table p, mantis_custom_field_table f WHERE p.project_id='7' AND p.field_id=f.id ORDER BY p.sequence ASC, f.name ASC
SELECT * FROM mantis_custom_field_table WHERE id='1'
SELECT name, type, possible_values, valid_regexp, access_level_rw, length_min, length_max, default_value FROM mantis_custom_field_table WHERE id='1'
SELECT name, type, possible_values, valid_regexp, access_level_rw, length_min, length_max, default_value FROM mantis_custom_field_table WHERE id='1'
SELECT value FROM mantis_custom_field_string_table WHERE field_id='1' AND bug_id='4048'
UPDATE mantis_custom_field_string_table SET value='' WHERE field_id='1' AND bug_id='4048'
INSERT INTO mantis_bug_history_table ( user_id, bug_id, date_modified, field_name, old_value, new_value ) VALUES ( '14', '4048', '2004-07-19 11:59:01', 'Client Name', 'XXXXX', '' ) |
|---|
