Referencing my ticket (for my own sake) https://support.zendesk.com/hc/requests/5032416
When you edit back end features like triggers for instance, the Save button only becomes enabled when there are unsaved changes. BUT, if you press refresh, the screen reloads without warning, and your changes are lost.
When you edit tickets, there is a small blue dot on the most recently viewed tickets, but you can leave the ticket screen without saving changes - there is very little visual indication of an unsaved change. BUT if you try to reload the ticket screen, you are warned of unsaved changes - and yet not WHICH changes are unsaved.
Having two different systems makes the process more difficult for user bases where staff might work on the back end AND the front end.
I would propose the best of both worlds... on the ticket view the refresh warning might remind users to look for the blue dot or link to a KB describing the process, AND the save button on a ticket should enable when any non-instant change is pending and unsaved (like adding a tag - which LOOKS instant).
On the back end, the system should probably warn a user of losing changes when they try to navigate away from a trigger or other edit which will be lost by that action.
The agent I was talking with couldn't think of a reason for the two different navigation methods - maybe there is one? Would appreciate feedback OR votes for the improvement.
Iniciar sesión para dejar un comentario.