This is a collection of UX/UI nuances I have noticed with Zendesk having used it for just six months. Many of these problems are (in my opinion as an experienced developer) not difficult to fix. Some obviously require longer consideration but I hope that having them listed in one place will initiate a feedback loop and encourage others to add their own.
The list will be updated/comments added as I encounter more.
Searching dynamic content
Searching dynamic content is the most perplexing search I have ever encountered. You cannot search by the DC tag (which would be incredibly helpful as that's what is referenced everywhere). You cannot search for the full title of the DC. You cannot search for part of a title. It appears that the search works on the content of the DC.
Automation dropdown/select boxes
The content of dropdown boxes when defining the logic in an automation is limited to 15 results with a completely unhelpful message reading "X other results. Try refining your search." Using groups as an example, I have over 400 groups. Many follow a naming convention (eg: BRAND - Legal Dept). So when I want to make a general inclusion/exclusion for all legal departments I will search for "legal". The select boxes in other areas of the system do not have this problem (eg: views) - they function perfectly by both filtering and listing all appropriate results, uncapped.
The caching on the site is short, but long enough to cause issues. If I am adding a new brand or area to the system I will add many views, groups, users etc. in quick succession. Having to wait a couple of minute after each submission turns a 15 minute job into a 60 minute job. Caching is obviously very important, but so is knowing when to refresh it. If I update a cached entity (eg: views), the entity should be re-cached.
Searching for groups seems to return exact matches only. Again, I have over 400 groups. Remembering the exact name for all of them is a chore.
We have prefixed a lot of them per brand which helps a little, but this does not scale.
Audit Log - searching filtering & listing changes
As per the title, the audit log is enormous but is unsearchable and un-filterable. There are also many entries that do not detail what was changed. I am aware you can search the audit log in the API, but this is about the web interface.
Number of suspended tickets in LHC capped
The number of tickets listed in the left hand column next to the name of the suspended tickets view appears to be capped at 5,000. This is misleading and unhelpful. The true value can be seen by opening the view and reading the value below the view title, but for taking in an overview at a glance I do not understand why this cap is in place.
"The tag cloud below is generated based on the 100 most used tags in the last two months. The cloud is updated daily"
Why 100? Why two months? I have far more than 100 tags and add more sometimes on a weekly basis. Some may only be applied half a dozen times but I still want to be able to view the associated tickets and potentially use the functions.
Also, the way the tags are displayed makes for difficult reading. A simple list would be far better.
댓글을 남기려면 로그인하세요.