Changing a request type in create screen doesn't update field values in some cases

Issue Summary

When changing a request type, default values for fields are respected, but when changed to a request type without default values for that field, the previous request type's value stays.

Steps to Reproduce

1. Setup 2 or more request types that use a field
2. Set a default value for a field on one of the request types
3. Don't set a default for that same field on another request type
4. Create an issue from within Jira (i.e., not in the portal)
5. Switch between the 2 request types and observe that the field retains the default value for the request type that specifies a default value (even when switching to the request type that doesn't have a default set)

Expected Results

The field is blanked when no default is set for a given request type

Actual Results

The field retains the value from the previous request type

Workaround

In the meantime, if it fits your use case, it is suggested to not set a default and instead set the field as required if it fits your use case to do so.