Use dashboards and insights

You will learn how to use project Insights and custom dashboards to monitor work without rebuilding the same reports every day.

Use issue views for individual records. Use Insights and dashboards for trends, rollups, and standing status pages.

Open Insights

Open a project and choose Insights.

Insights shows project analytics that refresh from the server and update after issue and sprint changes.

The page includes:

A cycle picker.
A Sprint Report link when the selected cycle has started or closed.
A triage strip.
Velocity, burnup, burndown, cycle time, and workload panels.

Read the triage strip

Use triage signals to find work that needs cleanup before planning. Triage usually points to issues such as:

Unassigned work.
Unestimated work.
Work that is missing planning context.
Status or ownership gaps.

Triage is most useful before sprint planning, backlog review, and weekly project health checks.

Read velocity

Velocity shows completed vs committed story points per closed sprint.

Use it to answer:

Is the team committing roughly the right amount?
Did completed work diverge from planned work?
Are recent sprints stable enough to inform future planning?

Do not treat velocity as a target to maximize. Use it as planning context.

Read burnup and burndown

Burnup shows total sprint scope vs completed points. It helps you see scope growth and completion progress.

Burndown shows remaining sprint points vs an ideal burn line. It helps you see whether the active sprint is trending toward completion.

Use the cycle picker to review the active cycle or past cycles. If scope changes mid-sprint, burnup often tells the clearer story.

Read cycle time

Cycle time shows how long issues take from in progress to done for recently completed work.

Use it to spot:

Work that sits too long after it starts.
Bottlenecks in review, testing, or deployment.
Whether changes to process are making flow faster or slower.

Cycle time depends on status hygiene. If issues stay in started statuses after work stops, the chart becomes less useful.

Read workload

Workload shows open issues by assignee.

Use it to find overloaded teammates, unbalanced assignments, or work that should be reassigned before a cycle starts.

Workload is a conversation starter, not a performance score. Check issue size, priority, urgency, and context before drawing conclusions.

Open a Sprint Report

When a selected cycle has started or closed, Insights can show Open Sprint Report.

Use the Sprint Report to review:

What was committed.
What completed.
What changed during the sprint.
What carried over.

Sprint Reports are most useful during retrospectives and planning for the next cycle.

For a complete review flow, read Close and review a sprint.

Create a dashboard

Open Dashboards from a project or workspace.

Choose New dashboard.

Use a dashboard when you want a standing page for a team, launch, project, or stakeholder group. Project dashboards are pinned to that project. Workspace dashboards can combine widgets across projects.

Name the dashboard for the audience or decision it supports, such as:

"Platform health"
"Launch readiness"
"Support triage"
"Sprint review"

For launch and release grouping, read Plan releases with milestones and versions.

Add useful widgets

Choose widgets that answer recurring questions. Good dashboard combinations:

Velocity plus burndown for sprint review.
Workload plus triage for planning.
Cycle time plus workload for flow review.
Project-specific widgets for a team dashboard.

Avoid dashboards that duplicate every chart. A good dashboard should make one standing conversation easier.

Manage dashboards

Dashboard cards show the dashboard name, icon, project context where applicable, and widget count.

Use the dashboard actions menu when you need to edit metadata or delete a dashboard. Deleting a dashboard removes the dashboard page; widgets attached to it may remain available depending on how they are stored.

Only people with the right dashboard permissions see write actions.

Review dashboards regularly

Dashboards become stale when a team changes process or priorities.

Review them occasionally:

Remove widgets nobody uses.
Rename dashboards when the audience changes.
Split one overloaded dashboard into focused dashboards.
Add a dashboard only when the same question keeps coming up.

If dashboard or automation notifications become noisy, read Tune notification settings.