Create Custom Dashboards

This document explains how to create custom dashboards in TestOps.

requirements

• You must have either the Project Admin or Test Lead role to create custom dashboards.

Overview

While pre-built templates provide core insights, TestOps's custom dashboards accommodate the need for monitoring more specialized areas as teams grow.

Custom dashboards can be designed to suit different purposes, such as:

• Sprint Review Dashboard: Curate widgets showing pass rates, execution trends, and failure categories filtered to current sprint for stakeholder review.
• Team Performance View: Combine execution volume, average duration, and status distribution widgets grouped by executor.
• Regression Suite Health: Monitor regression test stability with pass rate trends, new failing tests, and average suite duration.
• Cross-project Monitoring: View data, detect issues, compare performance, and standardize monitoring across multiple projects.

Create custom dashboards

1. Go to Project > Analytics tab > Dashboards.

2. Click on Create Dashboard. The screen displays the widgets that you can add or remove from the dashboard.

3. From the Widget Library, drag and drop widgets into the dashboard. You can also create custom widgets if existing widgets don't address your needs.

4. Select a project or multiple projects to retrieve data from.

If any project does not contain matching data for any widget, it will simply contribute zero records without affecting data from other projects.

5. Select dashboard scope and filters.

When a dashboard filter is applied, the final data shown in each widget is the result of filtering the original data through:

1. Widget Filters
2. Dashboard Filters
3. Selected Scope (time range or release/sprint)

If these filters conflict, widgets may display incomplete or empty data. For example, a widget designed to display only data from "Executor A", may not show any data on a dashboard filtered by "Executor B".

6. Click Save Draft to save the dashboard as a draft (private), or click Save and Publish to make the dashboard editable/viewable to people with access to the same project.

warning

• Published custom dashboards can be edited by different users and cannot be made private again.

Click Discard if you don't wish to save.

Best practices

Follow these tips to ensure correct data display.

Planning your dashboard

• Pick one scope type (e.g. by release X, by date range X-Y, ...) and one analytical intention (e.g. KPI tracking, performance tracking, defects tracking...) per dashboard, to ensure consistent data interpretation and avoid inconsistent metrics.
• Give your dashboard a clear name that reflects its intention and refer to it as you add widgets, to avoid scope-breaching.

Choosing filters

• Create new widgets if existing ones don't share the same analytical perspective with your dashboard.
• Keep widget filters neutral for reusability.
• Double-check for filtering conflicts by hovering on the Applied Filters icon:

Choosing projects for one dashboard

• Select projects one-by-one first to see if data display matches your expectation, before multi-selecting.
• Choose projects that share workflows and configurations, for consistent data across metrics.
• Avoid mixing projects with different lifecycle models.