UX: VSD/AI Impact should support dashboard wide filters

About

Currently the Value Stream and the AI Impact dashboards do not support dashboard wide date range filtering. The dashboards instead have date ranges defined for each panel.

The groupoptimize dashboard behavior should be consistent with groupproduct analytics dashboards that do support dashboard wide filters.

VSD	AI Impact

Example of dashboard wide date range filter

Questions:

• How do we handle the table columns in the comparison metrics visualization when dashboard-wide filters present?
• Right now the different dashboards are using fixed 3-month or 6-month time frames, with different time periods for the trend line.
• How do we handle time frames of Last 3 months vs. Last 90 days?

Proposal

TBD by @lvanc

1. Trend sparklines should use the same date range as seen within the table columns
2. ...

added gitlab-org#15329 as parent epic

mentioned in epic gitlab-org#15329

changed the description

added UX design-weight3 groupoptimize labels

added devopsplan sectiondev labels

set weight to 3

changed milestone to %17.7

added workflowready for design label

added severity4 label

@lvanc I think this might be a good time to step back and re-evaluate our approach to building Optimize dashboards/tiles.

The problem: Up to this point, we've been designing ad-hoc tiles for specialized purposes. Taken together as a collection, they don't really follow the logic or rules of a generic dashboarding framework, which is one of our long-term goals (Cross-stage Dashboards Vision & Roadmap to foun... (&13801)).

What do you think about stepping out of the current VSD use cases and tackling the dashboard framework a bit more generically? I think it would be an excellent first step to:

1. Inventory our current re-usable visualizations and document them here (https://design.gitlab.com/patterns/dashboards/)
2. Inventory and document current interaction models.
3. Look at this problem a bit more holistically. More on that below...

Thinking more broadly about dashboards:

• Should a dashboard be controlled by a single date range filter or should each tile get its own filters and date range selection?
• What controls should we surface for aggregation ranges (e.g. hour, day, week, month, quarter, ...) and should these be on a per-tile or dashboard-wide level?
• How can we enable users to add/remove tiles, visualizations, filters, date ranges, titles...in the UI instead of via YML? (Remove the need for visualization files from an... (#497577 - closed))
• What are some standard interaction models dashboards should support for things like drilling down into a subset of data/items? Customers are frequently left asking questions about what events/objects contributed to a specific metric on a dashboard.
• How can we increase the "eye candy" sentiment on the dashboards? Right now, they are not very interactive and not visually appealing.

TL;DR: I think we need to define the goals and constraints of the dashboard framework before we go in an figure out how to solve this specific problem of adding a dashboard-wide date range filter. WDYT?

FYI @blabuschagne @mushakov

@gweaver Completely agree! I have been wanting to work through this for some time now. I know that we have some open issues related to the dashboard panels but nothing related to looking at this problem more holistically.

I opened a new issue for this effort so we can continue the discussion there: UX: Dashboard framework vision (#500216).

/cc @blabuschagne @mushakov

added typemaintenance label

mentioned in issue #470881 (closed)

marked this issue as related to #470881 (closed)

mentioned in issue #499588

marked this issue as blocked by #500216

mentioned in issue #500216

added workflowblocked label and removed workflowready for design label

removed milestone %17.7

Closing this issue since this is a larger issue that will be worked through in UX: Dashboard framework vision (#500216).

closed

added devopsmonitor label and removed devopsplan label