Filtering allows you to refine your dashboard’s insights and drilldown to focus on a specific subset of data.

Dashboard filters are a good way to simplify insight configuration, eliminating the need to repeatedly apply the same filters to each insight within a dashboard.

Dashboard filters are easy to use, making them particularly suitable for sharing a dashboard with team members or stakeholders who are less proficient with the Keypup platform.

Dashboard filters are commonly used to filter on:

A date range (reporting range)
A specific user or list of users (team-level filtering)
A specific project (project-level drill down)
A list of labels (feature vs bug segmentation)

Where to find and configure dashboard-wide filters?

Once enabled, dashboard filters appear at the top of your dashboard, just above your insights.

All dashboard templates are pre-configured with filters. You can edit the value of each filter by clicking it.

If you see no filters, it means none have been created for this dashboard. See our next section to learn how to add filters to your dashboard.

Create and apply dashboard filters

Dashboard filters can be created by any user who has Owner or Editor permissions on a dashboard.

To add a new filter, click on the New filter button at the top right of your dashboard. This will open the dashboard configuration window.

The following must be completed to create a filter:

Filter name	The name that will show on the dashboard as an indication.
Type	The type of input. A filter can only apply to fields having the same type E.g., a date filter can be applied to an insight on `created_at`, to another insight on `merged_at` but cannot be applied to an insight `author` field. The following types are available Date or time range Number Text only Text/Text list Single user Single/Multi-user
Link filter to each insight	For each insight, specify the field that the filter will apply to. Read more here and see examples here.
Value	An optional initial value for the dashboard-wide filter.

Once completed (see configuration examples below), click Create filter at the bottom right of the modal to save it to your dashboard.

You will be redirected to the dashboard in edit mode. Click Save to save the dashboard and filters in the current configuration.

Bulk-selecting a field for the links

After selecting a linked field, a clone button will appear next to the dropdown, allowing you to apply this field to all pending links.

Insights using a dataset that does not support the cloned field will be skipped.

Locking or hiding a dashboard-wide filter

Whether you are creating or editing a filter, several options are presented at the bottom of the configuration modal to customize the usability of your filters:

Lock filter: when locked, the filter is read-only and appears on the dashboard with a lock icon. The filter's value can only be edited by editing the dashboard, then clicking on the filter to edit its configuration. This means only users with editor access on the dashboard will be able to edit locked filters.
Hide filter: when hidden, the filter only appears when editing the dashboard. Here again, the filter's value can only be edited by editing the dashboard, then clicking on the filter to edit its configuration. This means only users with editor access on the dashboard will be able to view and edit hidden filters.

Locked filters appear as read-only on the dashboard:

Hidden filters are only visible in dashboard edit mode:

Restricting a filter to allowed values

On Text only and Text/Text list filters, the Restrict to allowed values option limits the values viewers can pick to a list you define. This is useful on a dashboard per team, where a Developer(s) filter should only offer the developers of that team.

Turn the option on at the bottom of the configuration modal, then pick or type the allowed values. Once restricted:

Viewers can pick one or several of the allowed values, and nothing else. The operator is set to equals any of (Text only) or contains any of (Text/Text list).
When no value is picked, the filter applies all the allowed values, so the dashboard always stays focused on them.

The values must match exactly. Pick them from the list of values offered by the linked fields, such as usernames, rather than typing display names.

Changing the filter type removes the allowed values. You can also ask the AI Agent to restrict a filter, e.g. "only offer the developers of my team in the Developer(s) filter".

Quickly edit dashboard filter values

You can quickly edit a filter value by clicking your filter

The changes will be immediately visible on your insight, but will not be persisted. This is useful to quickly report on another value without changing the default configuration for future uses.

Users with the Owner or Editor role on a dashboard can click the Save button to persist the new value, which therefore becomes the default value (read here how to change other configurations).

Edit a filter configuration and insight mapping

This section is addressed to users with the Owner or Editor role on a dashboard.

To edit the configuration of a filter, click on it, then click on the cogwheel.

You can edit any of the configurations and save them to override the former configurations by following the same process as creating a filter from scratch.

Visual edition for insight mapping

This section is addressed to users with the Owner or Editor role on a dashboard.

There is another, more visual approach to editing the mapping of insights on dashboard-wide filters.

From the Edit dashboard layout mode, click a filter name to show how it is linked to each insight on the dashboard.

You can use the dropdown on each insight to change a mapping, then save your dashboard to apply it.

Precedence over insight filters

Dashboard-wide filters superimpose and take precedence over insight filters.

If an insight is configured with author = john.doe AND type = pull_request and a dashboard-wide filter author = bob is applied on top, the resulting filter will be author = bob AND type = pull_request.

This order of precedence also applies to non-dynamic drilldown filters. Dynamic drilldown filters (filters referencing the selected data point) are never overridden by dashboard-wide filters.

A filter restricted to allowed values with no value picked overrides the insight filter with all its allowed values.

Insights filters only get overridden by dashboard-wide filters when viewed on a dashboard. When edited or viewed standalone, the insight preserves its native filters.

Set up dashboard-wide filters