Issue Summary

This appears to be an edge case:

When the Description field of a request type assigned to Email is changed to Hidden with a preset value, no validation is performed and the configuration is saved. As a result, incoming emails fail with the following error:

"The associated request type does not have a visible Description field"

Steps to Reproduce

1. Open two browser tabs:
   1. Tab 1 – Open the request type that will be associated with Email.
   2. Tab 2 – Open Space settings > Email 
2. In Tab 2, set the Email request type to the request type opened in Tab 1 and save.
3. Without refreshing Tab 1, edit the Description field:
   1. Select Use preset value and hide from portal.
   2. Enter a static description.
   3. Save the request type.

Expected Results

If a request type is associated with Email, its Description field should not be allowed to be hidden as it breaks the email processing.

Actual Results

When the request type associated with Email has its Description field set to Hidden:

1. The configuration is saved without validation.
2. Incoming emails fail to create requests with the error "The associated request type does not have a visible Description field"

Workaround

Once a request type is associated with Email, the Description field cannot be edited directly to make it visible again.

To restore Description field to visible:

1. In Space settings > Email, temporarily change the Email request type to a different request type.
2. Open the original request type and update the Description field to make it visible again by unselecting "Use preset value and hide from portal"
3. Save changes
4. Reassign the original request type back to Email.