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.
For about the last week we have been seeing tickets randomly show the "Ticket Created from Thread Entry" record in some tickets. It is showing an actual ticket number that does indeed exist but it wasn't created by any of the technicians. In fact it shows the "System" user did this. I found an old support forum thread in the OSTicket website where ntozier mentioned that the "System" account shouldn't be allowed / be doing this and only technicians can created new tickets from existing threads, so I am not too sure what is going on there ( https://forum.osticket.com/d/93677-ticket-created-from-thread-entry). Like I said, it just started happening for the last 5 or so days I would say and we have been on the same version of OSTicket for a few months now and no configuration changes have taken place either.
Hi Stephen,
That is extremely odd, and rather unnerving I'm sure.
I would be happy to provide an answer if I had any idea what is going on. But as you probably realize it is extremely unlikely -- whatever is going on -- that it is a glitch introduced by osTicket Awesome.
Your best bet is to continue looking for solutions in the osTicket Forum or GitHub page.