Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen
Dashboard Tabs and Unwanted Query Duplicates
Gepostet 28. Feb. 2020
We recently completed a metrics audit for our instance and began 2020 by publishing a new series of dashboards for the agents and managers in our Zendesk instance.
To keep things simple, we created a series of what we called 'master queries', which we applied across multiple tabs in our dashboards, then filtering them to achieve the granularity required on each tab (like creating one 'master' CSAT query, and then filtering it for individual channels (support, chat, voice, etc) in dedicated tabs for these channels).
The behavior we expected was that this 'master' CSAT query would remain singular, so we could edit one query and the changes would then propagate to our tabs, then being limited according to the filters we established. However, on publication, the tool duplicated this 'master' query and created a new, copied query for each tab:
This unwanted copying turned our attempt to save time and streamline our Explore instance into a confusing mess. Instead of a few, easily editable 'master" queries, we have a messy list of indistinguishable copies.
5
3 Kommentare
Allison Ramsey-Henry
I am also running into this. I don't want a separate query for each user who needs to view it- is there a better way to do this?
0
Allison Ramsey-Henry
I just realized that when I was cloning my dashboards and tabs I was leaving "Clone Query" selected- that is probably causing the problem. I just created a clone without that checked and I think that solves the problem.
0
Joshua Bentley
Adding my vote for an improvement here. Yes, we can choose not to clone reports when cloning an already-existing dashboard, but forcing duplicate reports when cloning a default dashboard is ludicrous. I have been cleaning up my extraneous reports from people doing this since I have well over 1000 reports now.
Either label the report on the default dashboard or give us the option as to whether or not we want to clone the report. My guess is that the need to clone reports is small. Personal opinion: make it something users do at the report level instead of forcing admins to try every Explore user in the org NOT to clone reports.
0