Reports & analytics
TaskFlow turns the work you track into insight — agile reports, dashboards, a roadmap with a Gantt chart, project portfolios, releases and time reports. These are optional features; you'll see the ones your administrator has enabled.
Reports
The Reports section is computed live and split into eight categories — the same items you see in the section's submenu. The category is part of the page address, so a link to a particular report can be shared as it is.
| Category | What's in it |
|---|---|
| Overview | Project summary (key numbers and the change against the previous period), status distribution, priority breakdown. |
| Flow | Created vs completed and the cumulative backlog growth; a cumulative flow diagram (CFD) — by status category, by status or by the columns of a chosen board; Cycle Time and Lead Time with average, median, P75 and P90. |
| Workload | Who is busy with what: queue, work in progress, overdue, estimates and logged time. Blocked issues live here too. |
| Time | Completed in the period: issues, story points, logged hours and the average time to complete. |
| SLA | The share of goals met on time, breaches, issues at risk, and the average response and resolution times. |
| Backlog | What has piled up: size, priorities, types, age, old high-priority issues; overdue issues separately. |
| Sprint | Velocity over recent sprints, Burndown with the ideal line and a forecast, Burnup — which shows when scope grew. |
| Custom | Your own slice: a metric (issues, story points, hours) × a grouping (project, team, assignee, status, priority, type, sprint, day/week/month). |
Filters and the period
The filter panel is shared by every report: project (or "All available"), team, assignee, status, priority, type, label, sprint — and the period: day, week, month, quarter or your own date range. Switching reports keeps the filters, so the same slice is easy to look at from several angles. On a phone the panel collapses into a "Filters" row with a count of what's applied.
Sprint reports need a single project and a chosen sprint — and they say so.
How the main numbers are defined
| Value | Definition |
|---|---|
| Cycle Time | From an issue's first transition into progress to its completion. Issues that never entered progress are left out — they don't count as zero. |
| Lead Time | From creation to completion. |
| Delay | Today minus the due date, for unfinished issues with a due date. |
| Period | A rolling window backwards: day — 1, week — 7, month — 30, quarter — 90 days. With your own dates, exactly that range. |
| Change vs previous period | A comparison with a window of the same length immediately before the current one. |
Not every number has a trend
Only values defined over a period are compared: created, completed, total at the end, overdue. Point-in-time numbers — in progress, blocked — show a dash: that is the state right now, and the product keeps no snapshots of past states. Reconstructing them "from the log" would mean showing a different metric under the same name.
Blocked issues
There is no separate "blocker" object in the product — the report treats an issue as blocked when it is unfinished and either has a "blocked by" link to another unfinished issue or sits in a status like Blocked / On Hold.
The reason is refined by a label such as blocked:customer, blocked:department, blocked:technical, blocked:data — then the summary shows not just how much is stuck but what it is stuck on. The keys are yours to invent: an unknown one is shown as it is rather than lumped into "other".
From a report into the issue list
Numbers in the reports are clickable: a click opens the issue list with the conditions already filled in — the very ones the number was computed from. They are visible in the builder, and you can adjust them and save the result as a filter.
What you see and what has to be enabled
- Reports cover only the projects you can access; administrators and managers see all of them. Asking for a report on someone else's project is refused rather than silently emptied: "zero issues" and "no access" are different answers.
- Hours and estimates come from the time-tracking feature, and the SLA report from the SLA feature. When a feature is off, the report says the data is unavailable instead of showing zeros: "SLA isn't configured" and "SLA met 0 % of the time" are not the same statement.
Export, printing and email digests
- The CSV button on a report downloads its table as a file Excel opens without encoding trouble (UTF-8, “;” separator).
- Print / PDF prints the section or saves it as PDF from the browser: navigation and filters stay out of the printout, and a header line shows the category, the conditions and the date.
- Email digest sends the report by email on a schedule — daily, weekly, monthly or on your own schedule, in a chosen time zone. Recipients are users, groups and, if your administrator allows it, external addresses. Subscriptions live in a separate Digests submenu item.
A digest doesn't widen access
The report is computed with the rights of whoever created the subscription, and a recipient who can't see every project in its conditions doesn't get the email. The form shows in advance who will be dropped and why.
Dashboards
A dashboard is a home page made of widgets. You can have several, one of them the default; a selector at the top of the page switches between them. In edit mode you set the name, the number of columns (up to three), each widget's width and the order — by dragging on a computer or with arrows on a phone. Until you build anything, the first four available widgets are shown.
Widgets are contributed by features, so the list depends on what is enabled on your instance. For example:
| Widget | What it shows |
|---|---|
| Open issues | Unfinished issues in the active project. |
| Sprint progress | Done and remaining in the active sprint — in issues and story points. |
| Filter result | The result of a saved filter: as a list or as a single number. The gear on the widget picks the filter and the mode. |
| Report widgets | A mini CFD, issues by status, cycle time and workload — for a chosen project and period, with a link to the full report. |
The "Filter result" widget can be added several times with different filters, giving you a summary: "my overdue", "waiting for approval", "bugs in the release". It stores no conditions of its own — edit the filter and every widget pointing at it changes.
Sharing. A dashboard can be shared with a group, a project or everyone (the last only by administrators and managers). Recipients see it read-only, with the owner marked, and the widget data within their own rights: sharing a dashboard doesn't open up anyone's projects. If the feature behind a widget is turned off, the widget simply disappears from the layout.
Roadmap and Gantt chart
The Roadmap shows a project's issues — or the result of a saved filter — on a timeline:
- an issue with a start date and a due date is a bar between them; with only one of the two, the bar is dashed as an estimate; an issue flagged Milestone is a diamond;
- bars move with the mouse: dragging shifts both dates, the edges change the start or the due date. Without a mouse, a click or Enter on an issue opens a panel with the dates, the milestone flag and the links;
- dependencies are "blocks" links: the dot to the right of a bar draws a new one. A successor that starts before its predecessor ends is highlighted in red. With auto-shift ticked, moving an issue offers to move its dependants (with a list, after confirmation);
- critical path is a tick box: critical issues and links are highlighted, the rest show their slack. A cycle of links doesn't break the calculation — a banner points it out;
- the scale is day, week, month or quarter; grouping is by epic, by assignee or none; non-working days are marked (with the SLA feature on, you can use its working calendar with holidays), and so are release dates.
Up to 1000 issues are shown at a time — narrow a larger selection with a filter.
Portfolios
Portfolios group projects into a "portfolio → programme (optional) → project" hierarchy — for people responsible for several projects at once. A portfolio's tabs:
- Summary — a RAG traffic light (green, amber, red) for every project and a total for the portfolio. The status is computed from overdue issues, missed milestones, lag behind the plan and risks; the thresholds are set in the portfolio settings. A manual override is possible with a mandatory comment, and the history of changes is kept;
- Projects, Milestones (planned and actual date, linked issues), Risks (probability × impact, mitigation, owner), Timeline and Settings; CSV export.
A project belongs to at most one portfolio, which also shows on the project's own Portfolio tab. You only see projects you have access to. A portfolio milestone is a separate object, unrelated to an issue's Milestone flag. Portfolios send no email: a RAG change and a missed milestone are events an administrator builds automation rules on. Portfolios have no budgets.
Releases
Releases (versions) group issues into a shipment:
- Create a release with a name, version, description and planned date.
- Attach issues to it — an issue can belong to more than one release.
- Move it through planned → in progress → released → archived.
- Use the release page to see what's included and prepare release notes.
Issues show which releases they belong to, so you always know what's shipping where. Creating releases and moving them through their statuses takes an admin or manager; attaching an issue to a release is open to any member. Publishing a release doesn't change the status of its issues — the workflow stays the team's decision.
Release waves
For products shipped to multiple brands or destinations, release waves coordinate rolling the same work out to each brand at its own pace. A wave is a matrix of issues × brands, with each cell carrying its own readiness status, and you can set statuses in bulk rather than cell by cell.
It's an advanced feature for multi-brand delivery; if you ship to one destination you won't need it. Administrators define the brand set and the wave's workflow scheme — its statuses become the cell states — in wave schemes.
Time reports
With the worklog feature enabled, logged time shows up in two places:
- Timesheet — a week or a month by day. The by issue mode shows your entries (edit them right in a cell or add a row by issue key), the summary mode shows people by project or group. A regular member sees only their own time; administrators and managers can see any employee and summary timesheets.
- Summary report (in the Admin area) — filter by project, person and date range to see where effort actually went.
Both the timesheet and the report export time to CSV for Excel. Entries and the total for a specific issue are on its time log tab — see Issues → Time tracking.
Which of these do I have?
Reports, dashboards, roadmap, portfolios, releases, waves and worklog are separate features an administrator turns on. If a page isn't in your navigation, it isn't enabled for your instance (the exception is the worklog summary report: it sits in the Admin area) — see Features & settings (administrators).
Where to go next
- Boards & sprints — the sprint data behind velocity and burndown.
- Issues & tasks — the links, estimates and time entries the reports read.
- Filters & saved views — where a click on a report number takes you, and where the "Filter result" widget gets its data.
See also
- Plugins → Feature catalogue — reports, dashboards, the roadmap, portfolios, releases, waves and worklog as separate features.
- Project configuration → Brands — the catalogue release waves are built on.
- Administration overview — where Wave schemas and the worklog summary report live.
- Features & settings — how to enable a missing feature (administrators).