Design: OOTB dashboards vs. custom dashboards controls bar

Problem to solve

In #220180 (closed) we redefined the "Add panel" workflow for custom dashboards.

As part of this issue we want to:

  • Arrange the actions available for OOTB and for custom dashboards in a way that creates more consistency and increases the discoverability of custom dashboards.
  • Define what an OOTB dashboard controls should look like to show that it's view-only.

Intended users

User experience goal

I want to quickly find and perform actions on my dashboard.

Proposal

In 13.3 we're introducing the "Add panel" action to custom dashboards. It means that starting 13.3 release the actions available for OOTB vs. custom dashboards will be as follows.

OOTB dashboard (for example Overview dashboard)

  • Add metric
  • Duplicate current dashboard
  • Star dashboard
  • Create new dashboard

Custom dashboard

  • Add panel
  • Edit dashboard YAML
  • Duplicate current dashboard
  • Star dashboard
  • Create new dashboard

Showing disabled actions in OOTB dashboards

In order to drive the usage of custom dashboards we will display the "Add panel" and "Edit dashboard YAML" action in OOTB dashboards, but disable them and show a tooltip on hover with an explanation to drive users to create custom dashboards and try out "Add panel" feature.

Adding "Duplicate dashboard" to custom dashboards

Currently, "Duplicate dashboard" action doesn't exist in custom dashboards. This will be implemented in further iteration. We should not show that action until it's available.

Custom dashboard Default dashboard actions (while we still have "Add metric") Default dashboard actions on hover
Default_dashboard_-_More_actions Default_dashboard_-_More_actions-1 Default_dashboard_-_More_actions-2

Designs on Figma

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Nadia Sotnikova