Updating an issue with user or list format custom field, currently having value that is locked or removed, clears that field
|Assignee:||Jean-Philippe Lang||% Done:|
This is the scenario:
- issue is created and an active user is selected from the drop-down of the custom field with "user" format
- that user is later locked
- attempting to update the issue now clears the selection from the custom field
This is also happening on custom fields with "list" format, after the custom field list is updated.
It should be up to the person updating the issue to decide if new value should be selected rather than system clearing the field.
#1 Updated by Jack Kurzecki about 4 years ago
This is a data loss issue.
The workaround is to never lock (remove from the system) users that are entered on "user format" custom fields and never remove entries from "list format" custom fields, but that forces us to keep invalid selections in the interface.