Editors and admins can clone dashboards. Cloning creates an editable copy of the dashboard and all of its reports. You can then modify the dashboard's reports or add new reports to the dashboard.
This article contains the following topics:
Knowing when to clone
When you clone a prebuilt dashboard, you also create copies of all the reports used in that dashboard. These cloned reports are stored in the corresponding default datasets.
Before you clone a prebuilt dashboard, check that nobody else has already done this. When the same prebuilt dashboard is cloned multiple times, it creates duplicate reports which can make finding the reports you want difficult.
When you clone a custom dashboard, you can control whether Explore creates a copy of the reports. Additionally, you have the option to create a copy of the dataset that the original dashboard reports came from.
If you're planning to simply add new reports to a dashboard, there's no need to clone the reports or datasets. However, if you want to customize the reports for the cloned dashboard in a different way than the original, you must clone the reports. Cloning the dataset is rarely needed. It's useful only if you want to separate the cloned reports in a different dataset.
Cloning a dashboard
To clone a dashboard
- Click the Dashboard icon () in the left sidebar.
- Click the Settings icon () to the right of the dashboard name.
- Select Clone from the drop-down list.
- Enter a name for the cloned dashboard.
- If you're cloning a custom dashboard, select whether you also
want to clone the dashboard's reports and dataset.
- Click Clone.
I don't seem to have the ... option next to my dashboards?
Can you confirm which plan you're on? Typically when a menu doesn't appear it means you're not on the right account type for it, but if you are on Professional or higher and aren't seeing it, we can investigate what else might be going on.
That will explain it then as we have only just started on the Growth Suite plan which I now understand does not have this facility.
Hiya, I hope this thread is still open.
I am working on different dashboards that should somewhat report on the same metrics for at least two different sets of ticket brands/groups. Within one dashboard, I want to have different tabs, also reporting on more or less the same thing but with different time increments.
More specifically I want to have Dashboard X for Brand and Group X, with a weekly tab, a monthly tab, and a real-time one for ticket status only.
I want to have the same on Dashboard Y for Brand and Group Y so naturally, I cloned things - reports, tabs.
Cloning works fine, however, if I update, let's say, the time filter/reporting period on the monthly tab which is a clone of the weekly one, both tabs show the same. I cannot show a weekly period in one tab and a monthly period in the other - both update to the same period.
The same goes for any report in more than one dashboard - they always synchronize.
How can I avoid this? What settings do I need to choose to get to this to work or do I have to recreate every single report manually?
Thanks for helping!
Hi Katharina Stöhr
Since these were cloned dashboards, it's likely that it also cloned how the time filter operates. I recommend checking out the time filter to see which data is it affecting. Might be worth following the best practices for using dashboard filters article to see which is included or excluded in your filter.
I want a copy of the standard Zendesk Support dashboard, but with each tab limited to a specific Brand. This is to share with an external vendor who only supports one of our brands. I want them to be able to view and use the dashboard in Zendesk (they have an account in our instance), but where they cannot select which brand to view and are only able to see the data for a specified brand. Is there a way to accomplish this without editing each report in the dashboard?
I'm afraid this is no possible at this time. Explore doesn't have an option to dynamically filter dashboards/reports based on the current user. For now, the only way to achieve this is to create separate dashboard for each audience.
If you have time, you can add to this discussion and if you can, add as much details on your use case here: Creating dashboards with current user variable. This is tagged as 'planned' but there's no definite timeline or details that we can share yet. It would be helpful if you can upvote and share your thoughts through that thread. Thanks Heather!
Running into a situation where a few admins have Cloned the default support dashboard and now my reports are cluttered with multiple reports of the same name. Trying to find the report I want to add drill down options too is becoming quite a large headache when I am staring at 5 reports all with the same name. And when I view the reports if I am not shared the dashboard I have no way to know what dashboard they are assigned to, so I have no way to rename the report to make it easier to identify.
I would like to make a suggestion that when cloning a default dashboard that it adds the name of the new cloned dashboard to the end of the report name to make it easier to identify without having to have the Admin go in and manually rename each report.
Also would be nice if there was a Role permission that would let me as the Zendesk admin see what dashboards each report is associated with even if I am not shared that report so I can help maintain the list of reports and stop it from being cluttered with large amounts of duplicate named reports.
Thanks for your feedback.
I've taken a look and found that other users are discussing similar needs here:
Dashboard Tabs and Unwanted Query Duplicates
You can up-vote that original post and add your detailed use-case to the conversation. Threads with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
Specific examples, details about impact, and how you currently handle things are the most helpful things to share to help our product teams understand the full scope of the need when working on solutions.
We truly value customer feedback and your voice and votes in the product feedback topics in the community help influence future Zendesk functionality.
Please sign in to leave a comment.