Jokendhar Ravi Wrap Text in drop down after New Look

After introducing New Look in Dynamics 365 sales and case management, the "New Look" enabled Case Type filed and case priority filed value are break down into multiple row. if it does not fit width of the drop down which creates confusion to the user that the value in the drop down showing as two rows for single value. In the "Old Look" value for the case type field is not break down into multiple rows even the field value length is more than the drop down width. Our customer is not happy about this design changes, we are suggesting to change the design of new look dropdown's for case type and case priority as same as "Old Look".

After introducing New Look in Dynamics 365 sales and case management, the "New Look" enabled Case Type filed value and case priority filed value is break down into multiple row. if it does not fit width of the drop down which creates confusion to the user that the value in the drop down showing as two rows for single value. In the "Old Look" value for the case type field is not break down into multiple rows even the field value length is more than the drop down width. Our customer is not happy about this design changes, we are suggesting to change the design of "New Look" dropdown's for case type and case priority as same as "Old Look".

The "Add to Queue" button is currently available in the email entity. by using this users are able to create new queue or add selected email form particular view to existing queue which is creating unnecessary tracking of emails to D365 and creating records. This redundancy creates confusion, as the functionality to add an email to the queue is not needed in this context, leading to an inconsistent user experience.

Proposed Solution:

Remove the "Add to Queue" button from the email entity. Queue management should be limited to appropriate sections of the platform, and the email entity should not offer the option to add emails to the queue, thereby reducing unnecessary clutter and ensuring consistency across the platform.