from the everyday other software solutions one is used to the fact that one can use placeholders with regard to filters. It is not efficient to filter based on the current date and have to edit the filter every day to manually change the date. Another example would be if you want to create a standard view for a group of employees and filter based on the current user. You wish you could build a single view and share it with the people you want, but no way! Zoho throws a wrench in the works, you have to hard-code the user as a filter criterion. Therefore you have to create the default view n times. In addition, you can not even copy the view. But that is another topic :-D
Efficiency: In most other software solutions, placeholders for filters are available. The lack of this feature in Zoho Desk forces users to manually edit filters based on the current date. This is not only time consuming, but also error prone. Placeholders could automate this process and make it much more efficient.
Usability: Another example concerns the creation of standard views for groups of employees and filtering based on the current user. In many other programs, it is possible to create a single view with dynamic filter criterions and share it with the desired people. In Zoho Desk, this functionality is missing, which significantly limits usability. Instead, users must hard-code the user as a filter criterion, which adds unnecessary overhead.
Scalability: the lack of placeholders makes Zoho Desk less scalable. This is especially problematic when it comes to using the software effectively in larger organizations or changing environments.
Consistency: having to create standard views multiple times to cover different users or conditions leads to inefficiencies and increases the likelihood of errors. Placeholders would allow users to create consistent and easily updatable views, which would improve data consistency.
Overall, it appears that the lack of placeholders/flexible filtering options imposes significant limitations on users and negatively impacts the efficiency, usability, scalability, and consistency of the software.
The fact that the first idea was published four years ago and no action has been taken despite repeated mentions of the issue in various posts raises some questions. It is certainly appropriate to question the reason for the lack of implementation of this useful feature.
In any case, it makes sense to revisit the issue, back up the suggestions with more details, and possibly encourage all comunity user to express their support in the form of votes and comments. This can help increase interest and priority for this feature and improve the chances of its implementation.
So to all: Please give this post the attention it deserves. Thank you :)
Links to the posts on the same topic: