Dashboards and reports
Dashboards collect widgets on one page. Reports answer one question about a project, a board or a query, such as how a sprint went or how long work takes. This page is for project members who read them and for people who build dashboards.
Reports are computed from recorded history, not from today’s state alone. Every count opens the search that produced it, with the same total.
Build a dashboard
Section titled “Build a dashboard”- Create a dashboard with a name of 1 to 120 characters and, if you like, a description of up to 500.
- Choose one, two or three columns. They stack on small screens.
- Add widgets, up to 20, and place each one in a column.
- Share it for viewing or editing with projects, groups or everyone. You can name up to 20 viewers and 20 editors.
Anyone who sees a dashboard can copy it and star it. A copy is private to the person who made it. Only the owner changes who can view or edit it, and only the owner deletes it. A save made from an older version is refused.
Each widget reads with the permissions of the person looking at it, so two people can see different numbers in one widget.
| Widget | Shows |
|---|---|
| Filter results | Work from a project, a saved filter or a query, with the columns you choose, up to 50 rows |
| Assigned to me | Open work assigned to the viewer |
| Activity | Recent activity, for one project or for all that the viewer can read |
| Pie chart | Counts by one field |
| Two-dimensional | Counts in a matrix of two fields |
| Created vs resolved | Work created and resolved per period, optionally as running totals |
| Sprint health | The state of a project’s sprint |
Refresh and data version
Section titled “Refresh and data version”A widget header shows when the widget loaded and how much earlier its cached numbers were computed. It also shows the data version, a number that every change moves on. You can set a widget to refresh every 15, 30, 60 or 120 minutes while the page is visible. If a calculation fails, the widget shows the error and not the previous numbers.
Read the reports
Section titled “Read the reports”The reports page says which work its reports cover. By default that is the whole project. If you choose a board in the project, the charts, statistics and time reports follow that board’s filter and name it in their answer. Sprint, velocity and flow reports always cover the whole project and say so.
| Report | What it shows | Details |
|---|---|---|
| Burndown and burnup | Scope, remaining and done work across a sprint | In story points (the default) or in work item count. Marks work added after the start and estimate changes. Reopening work raises the remaining total. |
| Sprint report | Committed, added, completed, not completed and removed work | Each total opens its work items |
| Velocity | Committed and completed work for each completed sprint, with an average | Latest 6 sprints by default, up to 50. A sprint without a start record shows as unavailable instead of a guessed number. |
| Cumulative flow | Work in each status at the end of every day | Also the most it held that day and how often work entered it, so reopened work shows. Up to 366 days. Days before exact history are marked. |
| Control chart | Cycle time of each work item | You pick the statuses (In Progress by default), how repeat visits count, and which weekends and dates to leave out. Shows a rolling average with its standard deviation, a data table and CSV. |
| Epic and version burndown | Scope, completed and remaining work day by day | Lists work added, removed, re-estimated, completed and reopened. Forecasts from the last three completed sprints. |
| Created vs resolved, recently created, average age, resolution time, time since | Counts per day, week, month or quarter | The page offers 14 to 365 days. Work that was resolved and reopened counts as unresolved. |
| Statistics | Work counted by one field, or by two in a matrix | Built-in fields and custom select, multi-select, user, group, checkbox and cascading fields |
| Time tracking | Original estimate, time spent, remaining estimate, accuracy and unestimated work | For all work or one version. Time logged in work logs you may not read is counted apart. |
| Workload | Unresolved work grouped by assignee or any statistics field | A pie by remaining estimate, or by count when nothing is estimated |
Sprint reports count story, task and bug work. Epics and sub-tasks are not counted. Completing a sprint freezes its ending record before unfinished work moves, so later edits cannot rewrite a closed report.
Limits of reports
Section titled “Limits of reports”- Cumulative flow, the control chart and the epic and version burndown use windows of at most 366 days.
- Epic and version burndown cover up to 5,000 work items. Time tracking and workload cover up to 2,000, and the work item charts up to 50,000. A larger scope answers 422.
- History analysis is bounded to 250,000 work items and 250,000 recorded changes per request. Beyond that the report answers 422 and shows no partial result.
- The history-based charts are cached for 15 seconds per person. Each answer carries its data version and computation time.
Exports and drill-downs
Section titled “Exports and drill-downs”A report’s CSV and its drill-downs carry the report’s scope, time zone, data version and computation time. They say so when nothing matched or when work has no estimate.
Project summary
Section titled “Project summary”The summary of a project shows work completed, updated and created in the last 7 days. It also shows work due in the next 7 days and overdue work, a status overview, priority and type breakdowns, and open work per assignee for up to 30 people, then unassigned. Each count opens a search with the same total. Answers are kept for 30 seconds, so relative dates can lag by that much.
Analytics for external tools Planned
Section titled “Analytics for external tools ”Analytics through governed data pipelines and connectors for business intelligence tools are planned for after launch. Nothing of this exists yet. Until then, use the report exports and the API.