This is an osTicket bug that they fixed in v1.17.1.
You should upgrade to osTicket Awesome for osTicket 1.17.1 (Revision 1), which includes the fix. Or upgrade to osTicket Awesome for osTicket 1.17.2 (Revision 1) when it is released later this week.
Until then you’ll have to clear your browser’s cache every time you encounter the issue.