Notifications
Clear all
6 Forums 829 Topics 3,280 Posts 8 Online 3,047 Members

Resolved Custom columns | Text overflow clipping not working

5 Posts
2 Users
0 Reactions
139 Views
Posts: 7
Topic starter
(@zomni)
Member
Joined: 5 months ago

Hello,
There seems to be an issue when trying to utilize the custom column text overflow behavior options (Text wrap, Clipping, etc.), specifically the text clipping option.
Attached are the OSTA and native osTicket displays.
Also the preview tab would be a great addition.
Thank you in advance.osta-view osticket-view


4 Replies
Posts: 7
Topic starter
(@zomni)
Member
Joined: 5 months ago

osTicket version 1.18.2


Reply
Posts: 7
Topic starter
(@zomni)
Member
Joined: 5 months ago

Re-Uploading pictures since the whole site migrated.


Reply
Posts: 7
Topic starter
(@zomni)
Member
Joined: 5 months ago

Native osTicket behaviour.


Reply
Posts: 1185
Admin
(@stevland)
Member
Joined: 10 years ago

Thanks for the detailed report and screenshots, Daniel.Thanks for the detailed report and screenshots, Daniel.

You're right. osTicket Awesome rebuilds the ticket list with its own responsive column layout, and in doing so it currently overrides osTicket's native Clip/Ellipsis behavior, so cells wrap instead of staying on one line. That's why your "Issue summary" column overflows in the list even though it clips correctly in the queue Preview. It's a real limitation on our side, and it's on our list to make these options work natively.

In the meantime, you can force one-line clipping by pasting this into Admin Panel → (osAwesome settings) → Custom CSS:

form[action="tickets.php"] table.list td .truncate {
display: block;
max-width: 100% !important;
white-space: nowrap;
overflow: hidden;
}
form[action="tickets.php"] table.list td .truncate:not(.bleed) {
text-overflow: ellipsis;
}

One heads-up: this applies to every column you've set to Clip or Ellipsis (including Subject), not just "Issue summary". There's no reliable way to target a single custom column, since columns can be reordered. And on narrow screens it'll cut text more aggressively. If that tradeoff works for your data-heavy view, it should do the job.


Reply
Share: