Conversation attributes now collapsed previews instead of fully displaying? | Community
Skip to main content
Question

Conversation attributes now collapsed previews instead of fully displaying?

  • August 14, 2026
  • 2 replies
  • 47 views
S

It seems there was a UI change recently that made all sidebar conversation attributes show only a few characters of preview and force you to click into each one-by-one to get the actual data inside. This is a big time drag when those fields get auto-populated for conversations and cannot be read by a support agent at a glance without clicking in and out of lots of individual fields. There doesn’t appear to be any way to go back to the old view where the fields were expanded by default. When did this happen, and can a configuration be added either globally or per field to have it fully expanded in the sidebar by default for ease of use on key fields? 

2 replies

Aleksei O
Super User ✨
Forum|alt.badge.img+5
  • Aleksei O
  • Super User
  • August 18, 2026

Hi ​@Shane Moriah ! Does changing the size of the right-hand side bar resolve the issue for you? 

Book a free call with me here: https://cal.com/alexeyox/30min
S
  • Shane Moriah
  • Author
  • New Participant
  • August 18, 2026

Hey ​@Aleksei O , nope that doesn’t fix it for me. It adds or removes a few extra characters as I expand/contract the sidebar but doesn’t change the display from having every attribute on a single line to allowing longform attributes to be expanded downwards across multiple lines. The text in many of these attributes is multiple sentences, so getting a couple extra words from expanding the sidebar doesn’t really help much. 

E.g. the text in one of them shows with sidebar at smallest size as “Hi David, thank yo...” and at largest size as “Hi David, thank you for the update and for flaggi...” but the full text paragraph requires clicking into the field then selecting the tiny text box expansion tool in the bootom right and dragging it all the way down to be able to just see that one field, and then doing it again for any other longform field and on every ticket. 

Terms & ConditionsAccessibility statement