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 creating a task from a ticket in the Awesome osTicket theme, it is possible to submit the form without selecting a Department. The form does not indicate that the field is required, and no validation message is shown. Instead, the system returns a generic error message: “Error adding task - Please try again!”.
In the default osTicket interface, the Department field is clearly marked as required and validation prevents submission. In the Awesome theme, the field is not visually marked as required and the user receives no indication of what caused the error.
This creates a confusing user experience because the form appears valid but fails on submission.
Hi @cbd4-dk,
Thanks for reporting this. You're right, and this is a bug on our end.
The Department field on the task creation form should be marked as required and should validate before submission, just like it does in the default osTicket interface. Instead, it fails silently and returns a generic error, which is exactly the kind of confusing experience we're trying to eliminate.
This will be fixed in the next point release. In the meantime, you can add this to your Theme > Custom CSS:
body.tickets-page #popup #new-task-form .error {
display: inline;
}
Appreciate you taking the time to document this clearly.