Anonymous
Forum Replies Created
-
In reply to: Client replies added in weird chronological order
By the way the screenshots above were made on the OSTA Client Demo.
In reply to: Client replies added in weird chronological order
In reply to: Client replies added in weird chronological order
Never mind!
I’ve managed 🙂
In reply to: Dark Mode Missing Logo in Top Left
true! +1
In reply to: Injecting custom JS
Hey @cartmega, are your plugins compatible with OSTAwesome’s themes?
In reply to: Add header/footer UI in admin panel
Hey @stevland thanks for the reply!
Our idea was not to change the current header, but to add on top of it our custom company-wide header.
In reply to: Add header/footer UI in admin panel
Hey @stevland, what do you think?
Being able to manage custom content inserted in header and footer (and perhaps use to be able to inject some JS). This would make it quite handy to make some visual changes (stored directly in the DB) without having to modify the code.
In reply to: Hide drop-down menu of help topics in new ticket
Hey Mauro,
I’ve recently been looking into achieving something similar, and found this mod that could answer your problem.
https://github.com/osTicket/osTicket/pull/5564
However I haven’t tested it yet!
Julien
In reply to: ticket thread
+1 on the great idea!
In reply to: no annotation in admin / tickets / queue / colums
Hey @stevland,
I was looking for that annotation tab too but read this thread so understood why it was removed 🙂
However I am interested in seeing the icon for the ticket source… Would this be something you’d consider adding in a future release?
Otherwise, any idea how I could get those icons/annotations back in?
Hey checking this further, I realize that the default condition that puts in bold the ticket ID and subject when the ticket is unread doesn’t work actually… it seems like the OSTA theming overwrites this style change by forcing a font-weight of 500….
In reply to: Injecting custom JS
hey little update…
We’re looking to have some sort of conditional fields in our forms. For example: if item B is selected in dropdown, then hide the next 3 fields.
We managed to build some javascript that can achieve this. However we’ve realized that the custom form/field names and ids are generated randomly and will change from one user to another (to prevent from spammers). Which makes our scripts irrelevant…I read some ideas about removing the bit in the code that rules the random generations, but I am not too keen to edit the core code.
So I am wondering if anyone has done this another way or has suggestions ?
In reply to: In-site translations not being applied
Hey @stevland, I was wondering, do you see a temporary workaround to still manage to get these translated?