Have you checked these first?
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
Note: Never paste the contents of your ost-config.php file here; it holds your database credentials.
Two quick checks before posting: try clearing your browser cache, and press SHIFT+O on any Staff Panel page to enter Safe Mode (a stock osTicket with no enhancements). If the problem still shows in Safe Mode, it's in osTicket itself, not osTicket Awesome. But let us know about the issue either way.
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
This forum is public. Never post order numbers, full license keys, email addresses, or payment details.
This is the place for general questions about how billing and licensing work — renewals, activation, staging slots, plan differences, and what happens when a license lapses.
For anything tied to your specific account, refund, or payment, contact us directly instead.
When adding conditional formatting, the priority "text" eg Low Normal High appears in the priority column which widens the priority column. I presume osticketawesome removes this text, but adding conditional formatting breaks this.
osTicket v1.15.1 // osTicket-1.15.1-Awesome-101
PHP 7.2.24 // MySQL 5.5.68 // Apache/2.4.6 web server


Hi @itcubed,
I have been working intimately with osTicket for close to a decade now, and people keep making me aware of features that I had no idea existed.
The ability to highlight rows based on conditions is something I hadn't stumbled upon.
In any event, it turns out this is a super simple fix.
I will include this in future releases, but if you want to implement it now add the following to Admin Panel > Theme > Custom CSS:
td.osta_priority div {
display: none;
}
That's it!
I see a couple of other minor glitches with the conditional highlighting on that I will try to resolve for the next release.