Issue Summary

Selected Request types gets over written by default request types settings when we enable default request types(in feature section) and try to create a request from portal when there is change in hierachy of the issue

Steps to Reproduce

1. Enable the default request types settings with values.
    
2. When you create an issue, its request types should be same. If due to some internal set up, there is update on its parent field, then the issue's request types are set to default request type values selected in above settings.
3. Reason is when parent field gets modified then there is changes in the breadcrum of the issue as below
   

Expected Results

Request types selected during the ticket creation should not get changed by the default values set in the Default request types settings due to other set up.

Actual Results

Currently, due to change in the fields i.e. parent field, the hierachy is modified and default values of request types are set from the default settings.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available