Defect #1516
Issue loses custom field values
| Status: | Closed | Start: | 2008-06-23 | |
| Priority: | High | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Custom fields | |||
| Target version: | 0.8 | |||
| Affected version: | devel |
Resolution: | Fixed |
|
Description
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 "<<custom field>> can't be blank" appears (which is correct)
- enter the ticket id in the search field to reload the page
- the issue's custom fields are blank (and no journal details are written)
- the issue should not have changed
History
2008-06-23 22:55 - Thomas Löber
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.
2008-06-27 22:15 - Jean-Philippe Lang
- Status changed from New to Closed
- Target version set to 0.8
- Resolution set to Fixed
r1592 should fix this problem.
Now if you do not post custom field in your request, no change is made.