Bookmark component for the new dashboard builder - Gathering interest

Épinglée

8 Commentaires

  • Shayan Moussawi
    • Why is the bookmark component important to you? What is the use case where this feature is most needed? How frequently do you use it?

    Currently using the Bookmark feature to sync filters from different datasets with each other without having to think about complex connections. 

    Also using it to remove "NULL" Values from Filters, which are really unprofessional to be display.

    • On a scale from 1 to 5, how impactful would it be if the bookmark component wasn’t available in the new dashboard builder?

    I would say 4. Pretty impactful unless there was another feature that would make it obsolete.

    Bookmarks help a lot by making filters more readable and syncing them from several datasets. 

    1
  • Joey Liew
    • Why is the bookmark component important to you? What is the use case where this feature is most needed? How frequently do you use it?

    I use the bookmark component to pre-select certain filter. Example, pre-select the Current Month for certain group of ticket. This feature is used few times every week. 

    • On a scale from 1 to 5, how impactful would it be if the bookmark component wasn’t available in the new dashboard builder?

    4 - without this feature, I would need to manually select all the filters before able to view the accurate data on dashboards. 

    0
  • Stephen
    • Why is the bookmark component important to you? What is the use case where this feature is most needed? How frequently do you use it?

    Bookmarks are heavily used across all Dashboards to ensure the correct data is always displayed when you access a tab.

    On some Dashboards, we have a series of hidden filters, which the bookmarks control what level of data is exposed.

    On some of our customer accessible dashboards, we use the bookmarks to ensure they can only select data for their organisation - we do not want customers to use an organisation filter to access other customers data.

    • On a scale from 1 to 5, how impactful would it be if the bookmark component wasn’t available in the new dashboard builder?

    5 - this is a fundamental feature used across all of the Dashboards we use in my organisation. Losing this function would effectively mean we need to look for an alternate approach to reporting in Zendesk.

    1
  • Ronald
    • Why is the bookmark component important to you? What is the use case where this feature is most needed? How frequently do you use it?

    It’s important to me in two ways. [1] So that I don’t have to select the same options over and over and over again as I review data for the same time period, ticket groups, etc. across multiple dashboard tabs. [2] The other way is in terms of how I can make a single report more useful in multiple dashboard contexts. I don’t have to create multiple copies of the same report to filter by a different ticket group each time, for example, when creating dashboards for different team managers. I can put the same report on multiple dashboards and then pin a bookmarked filter in a hidden widget and select the ticket group filter that way in each dashboard.

    • On a scale from 1 to 5, how impactful would it be if the bookmark component wasn’t available in the new dashboard builder?

    I would say 4. I would still be able to get at the data I need but it wouldn't be convenient. I appreciate that y'all are asking for feedback, and I guess on a superficial level I can understand why maybe this feature doesn't seem super critical next to some of the rest of what's involved. But to anyone who uses these reports on a regular basis, and I suspect that's most Zendesk admins, removing this capability will create a lot of acrimony.

    1
  • CJ Johnson

    Removing this feature would be an absolute dealbreaker. 

    Zendesk Support has repeatedly advised us to put filters on Dashboards, not reports, to keep reports from timing out. This means that bookmarks are critical to the reports on the Dashboards returning useful information for a desired timeframe, since the reports themselves are no longer filtering. Without bookmarks, we'd be stuck getting emails of "all history to all history" instead of the needed yesterday or last week.  

    Removing Bookmarks would necessitate us re-writing literally hundreds of reports, and rebuilding about a dozen Dashboards. Given how many ongoing, unresolved issues we already have with Explore, I would advocate for us using literally any platform for reporting other than this one, if this is removed. 

    2
  • Tom Erik Skjønsberg

    I am with CJ Johnson on this one.

    Removing bookmarks would mean we stop using Explore and most probably Zendesk alltogether. Removing another basic functionality, and with this one that Zendesk themselves have been telling us to use for years, would be a quick dealbreaker.

    1
  • Rafa Dobón - CS Team Leader

    It's a must have.

    0
  • Ola Timpson

    Our main usage of bookmarks is currently to set default filters for a dashboard, so that we can use generic queries but not have the dashboard load all the data on launch. We also use it to tidy up filter options.

    Impact of losing would be a 4 out of 5 in terms of functionality, but the bigger impact would be loss of respect from stakeholders across the business when we explain they now have to click more.

    1

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk