This privilege, right here determines what tickets I see. If 'ALL', and only All, is enabled, I can see the suspended tickets view. If I flip that to any other option, the suspended ticket view goes away. I can't allow the agents in this position to see All Tickets because sometimes tickets have very sensitive material in them and I can't allow them the ability to search and find those. Specifically sensitive HR-related tickets. I understand why that privilege takes away the view but that is FAR too rigid - agents should be able to see spam received at their support address, recover spam, and mark spam. If it's received at the brand support address, why can't you allow agents to only see suspended tickets that came to their support address? That seems really logical to me. But if I instead flip this privilege to allow them to only see tickets in their group (which is what I want), the suspended tickets view goes away for them and that now means that I, the administrator, an IT project manager, has to go in and monitor that view constantly. This is a terrible situation for both me and the manager. I don't want to waste my time doing something so petty, I have a million other responsibilities to manage. I want the manager to be autonomous and do that on their own. There should be a stand-alone privilege for accessing the suspended tickets view for tickets received at each team's associated support address. Additionally, if I flip that form ALL to any other options, agents cannot mark tickets as spam themselves!! How ridiculous that they cannot at least mark a ticket as spam. I need this as a stand-alone privilege to view, recover, and market suspended tickets.
Vous devez vous connecter pour laisser un commentaire.