How do we ensure consistent layout? For example, one of our most important fields is only present on certain request forms, where it's essential for client selection.
The issue arises because this field is grouped with other important custom fields on the service tab of the screen. This grouping only occurs unless the incident was NOT submitted through a request form that includes this field.
Consequently, this leads to inconsistent layouts within a single issue type, where the field's position is not determined solely by the screen configuration.
We're facing challenges with how the request form has become so prevalent in the cloud environment.
Can someone explain why there's been such a drastic shift compared to server behaviour?
Also, we have a concern about the 'requested participants' field, which consistently fails to appear on the create screen
