1:18.3 (and earlier versions) Truncating Issue Summary

MS1Corp

Seems that truncation occurring on Custom Queue for some but not all tickets, that display accurately in the Open (ootb) queue.

What is happening and how do we stop this?
The custom queue has a condition to change bgcolor when Answered == false

There is overlapping tickets on the screenshots, to illustrate they should appear the same (both should display the full issue summary, or more than the first letter)

KevinTheJedi

MS1Corp

Hmm.. do you have any mods? When we add ellipsis it's always three dots (...); not two as shown in your screenshot. Maybe a language pack thing? Do you have any language packs installed?

Here is a test I just did in my own instance. When a column's width is not long enough for text and the Text Overflow setting for that column is set to "Add Ellipsis" it will add three dots. You can change the Text Overflow setting for each column under Admin Panel > Settings > Tickets > Queues > click your queue > Columns > Config (next to the desired column) > Data > Text Overflow.

Cheers.

MS1Corp

For the benefit of others, this was an administration configuration mistake.

Our admin thought that the column width setting was CHARS, but it appears to be PIXELS.
When the column width was set to 20, it was truncating down to a "C.."

Is there documentation that explains how the pixel widths are prioritized?
E.g. is the width of the leftmost column is enforced by sacrificing all downstream column widths to be narrower if necessary, then the next column is evaluated to see if it fits before sacrificing downstream columns, etc.

We're having a hard time shaping the columns.
TIA

KevinTheJedi

MS1Corp

Each column should respect their own size. The columns should simply shift off the page to the right if total table width is too wide (overflow). Of course in that case it’d be scrollable.

Cheers.