Issue Summary

This is a regression of JSDSERVER-1926

Custom field assumes default values even if the field is set as empty on customer portal.
On the create issue screen, the field can be set as empty and once the issue is created the field will remain empty.
However, on Customer Portal, even if you set the field as empty, the issue will be created with the default value set.

Steps to Reproduce

1. Create a custom field, for example a checkbox and set a default value
2. Add the custom field to the corresponding screen and request type field
3. Create a request via Customer Portal with the custom field unchecked
4. As comparison, create an issue via the Create Issue screen with the field unchecked

Expected Results

The created request will not have the custom field value set because it was unchecked when creating the request.

Actual Results

The custom field default value is set.
As comparison, when the custom field value is not set when the issue is created via Create Issue screen.

Workaround

Don't set a default value for the custom field

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: