Forum Replies Created
October 19, 2023 at 5:11 pm #18522
I cannot reproduce the issue on my end. The password reset function works perfectly.
I’m not sure if it matters, but have you checked your Helpdesk URL?
Admin Panel > System and Settings > Helpdesk URL.
If you look at vanilla osTicket 1.14‘s Advanced Search > Columns you’ll see that you can add Columns.
But starting in osTicket 1.15 they revamped the way Advanced Search works, and there is no longer an option to add columns. I’m not sure what the purpose of the “use standard columns” checkbox is because, yes, in my experience it is always greyed out.
In short, this is not an osTicket Awesome issue, but rather an upstream change that the osTicket devs have made.
If you wished to pursue it I would suggest opening an Issue on GitHub.
Thank you for the reports!
This issue has now been resolved in the latest release osTicket Awesome for osTicket 1.18 (Revision 3).
Wow Julien, that’s really weird.
Even stranger that I can’t reproduce it.
From the Client side I added a reply to ticket 235.
And then on the Staff side my reply showed up in ticket 235 at the bottom as expected.
Of course, if you visit those links my reply will be gone because the database resets every hour.
Either way, very odd.
Are you still experiencing this in your own installation?
What happens if you press SHIFT + O on both sides?
Es befindet sich immer noch am selben Ort, aber Sie müssen zuerst auf die Schaltfläche „Mehr“ klicken.
If you look at vanilla osTicket 1.14‘s Advanced Search > Columns you’ll see that you can add Status.
But starting in osTicket 1.15 they revamped the way Advanced Search works, and there is no longer an option to add columns such as Status.
Therefore, this is not an osTicket Awesome issue, but rather an upstream change that the osTicket devs have made.
If you wished to pursue it I would suggest opening an Issue on GitHub.October 19, 2023 at 3:57 pm #18507
I tried to reproduce that issue.
Using the 1.17.3-2 Demo I selected the logo that is closest to the shape of your logo.
I then adjusted the browser window to try and find a resolution that would trigger the issue.
Sorry, I’m just not seeing it.
I’m wondering if your logo has transparent space around it, like the 1st example on this page?
I feel you. It is also a pet peeve of mine when applications don’t support keyboard navigation.
Having said that, I made a form over function design decision years ago when building osTicket Awesome.
Design is all about trying to have control over details, and the fact is that the functionality that allows you to see what field is in focus is implemented differently in every browser; and the only thing that remains consistent through every browser is that it always looks ugly.
Therefore, I eventually figured out how to neuter it.
What I have done now for you is I have tried to figure out all the lines of CSS I used to neuter it, and segregated all of that code into one section.
If you open /osta/css/staff-desktop.css and replace its contents with the contents of this Pastebin, you can then scroll to the bottom of the file and delete the section titled, “SUPRESS BROSWER OUTLINE”.
Once you save it you should find that the TAB functionality you seek will work as you expect. You may have to clear your browser cache.
And when you upgrade osTicket Awesome in the future you will have to open staff-desktop.css and delete that section again.
I may eventually add this as an Accessibility option in the Theme section.
Search canned responses, original user can click canned response and the cursor goes to the search board.
I couldn’t figure out what you’ve tried to say here. If it still feels important feel free to give me directions on how to find the area you are referring to, or perhaps a link (e.g. /scp/canned.php)
Unfortunately I am having a hard time visualizing your setup.
A screenshot would probably go a long way to helping me understand your application.
And what happens when you press SHIFT + O? Do your Queues display elegantly in vanilla osTicket?October 19, 2023 at 1:48 pm #18490
Thank you for taking the time to also point out that the issue occurs in regular osTicket.
But actually, I can’t reproduce it in either environment!
What browser are you using?
@rglfsucu is probably correct… there is likely a setting somewhere that you can enable to allow notifications to all of the agents.
I am an one man operation, so I have no experience using osTicket collaboratively.
And, either way, this is actually an osTicket question, not an issue with osTicket Awesome.
You’ll chances of finding a helpful response would be a lot higher if you posted this question in the osTicket Forum.
I’ll mark this as ‘Resolved’, but if you can still reply if you wish to.
Thank you for understanding.October 19, 2023 at 1:32 pm #18488
I’m sorry for the very late reply.
And you probably aren’t going to like this response, but it is extremely unlikely that this issue was introduced by osTicket Awesome. It is an upstream issue with osTicket itself.
Please see this issue report for more information and some possible fixes.
I will close this for now, but if you still feel for some reason that it is an issue related to osTicket Awesome you can still reply again.
Thank you for understanding.
That’s a really weird issue!
It’s only affecting one of your users? And they can’t even click the button?
Please ask them to try using a different web browser temporarily to see if the button becomes clickable. Let me know if that helps.