Flow: reports, SLA and business calendar
Flow reports answer "how many", "how long" and "did we make the deadline": how many tasks there are by status and assignee, how many deals reached negotiation, whether the team will close the sprint in time, how many days a ticket sits in "Approval", what share of requests was closed on time. This article covers the "Reports" section, SLA deadlines and the workspace's business hours.
The "Reports" section
The "Reports" item is in the workspace's left column. The section has six tabs:
Tab | What it shows |
|---|---|
"Dashboard" | Tiles with numbers, charts, funnels and burndown; personal and shared dashboards |
"Funnel" | How many objects reached each process stage and the conversion between stages |
"Burndown" | How much work is left on each day of the period, plus the ideal line |
"Time in status" | How long a type's objects spend in each status |
"SLA" | The share of objects that met their deadline and a list of breaches |
"Time tracking" | How much time is logged on objects: by person, by object or by relation |
A combined report across all workspaces is in "All workspaces" mode — see Flow: all workspaces.
Reports are calculated with your permissions: they include only objects you can read. A field hidden from your role on even some objects can't be chosen for grouping or summing — otherwise the total would reveal hidden values. Archived objects aren't included in number tiles; the funnel and burndown take their history into account, because those are reports about the past.
Dashboard
A dashboard is made of tiles. Each tile is a single number, a chart by group, a funnel or a burndown. Dashboards are stored on the Flow server: your dashboard is the same in any browser and on any device.
Personal and shared dashboards
The list at the top of the tab switches between dashboards and is split into "Personal" and "Shared" groups.
Dashboard | Who sees it | Who changes it |
|---|---|---|
Personal | Only the author | The author |
Shared | All workspace members | The author and workspace administrators |
"New dashboard" creates a dashboard: enter a "Name" and, if needed, check "Shared — all workspace members will see it".
"Rename", the trash icon ("Delete dashboard") and the "Shared" switch are visible to those who can change the dashboard. If you uncheck "Shared", the dashboard becomes the author's personal dashboard.
Roles with permission to configure views can share dashboards: by default the owner, administrator and member (a member only their own dashboards). Any workspace member, even a viewer, can create a personal dashboard. A personal dashboard doesn't make someone a paid staff member.
A workspace can have up to 100 shared dashboards, one person up to 50 dashboards, and a dashboard up to 50 tiles.
A shared dashboard shows everyone only their own data: tiles are calculated with the viewer's permissions. A colleague without access to deals sees empty or smaller numbers on a shared dashboard, not other people's deals.
New workspaces created from the "Tasks" and "CRM" templates already have a shared dashboard — "Tasks" or "Sales" (with a funnel by deal amount).
If there are no dashboards yet, Flow shows a starter set based on the first type with statuses: "total", "by status" and "new per week" over 90 days. As soon as you change it, it is saved as your personal dashboard.
Tiles used to be stored in the browser. The first time you open reports, such tiles are moved to the server once as a personal dashboard called "My dashboard", and the browser copy is deleted. If the move fails, Flow shows an error with a "Retry" button, and the tiles aren't lost.
Changes are saved automatically. If the dashboard was changed at the same time in another window or by a colleague, Flow offers "Reload" or "Save my changes".
Tiles
The "Tile" button adds a tile, and the icons on a tile are "Move up", "Move down", "Configure tile" and "Remove tile". In the tile settings you first choose the "Kind": "Number or chart", "Funnel" or "Burndown". A funnel and a burndown are configured the same way as on their own tabs (see below); a burndown tile can have its own "From" and "To" dates or count up to today. Settings of a "Number or chart" tile:
Field | Options |
|---|---|
"Object type" | Any type in the workspace |
"Filter" | "All objects" or a saved view of the type: the tile uses its condition |
"Created" | "All time", the last 7, 30 or 90 days, or the last year |
"Group by" | "No grouping — a single number", "By status", "By assignee", "By author", "By week created", "By month created", or by a type field (string, select, checkbox, member or members; a date field — by week or month) |
"Metric" | "Amount", "Sum" or "Average" of a number or money field |
"Name" | Optional: Flow suggests a name itself |
Details:
An object with several values (for example, several members) is counted in the group of each value, but only once in "Total".
Money amounts in different currencies aren't added up: the tile shows "mixed currencies".
If there are more groups than fit, the tile shows the largest ones: "Showing the largest groups — the rest didn't fit."
Weeks and months are calculated in UTC.
The server rejects a report that is too heavy for a large type; narrow the selection with a view or a period.
Funnel
The "Funnel" tab shows how objects move through process stages: how many new deals became qualified, reached a proposal, reached negotiation and were won. Choose the "Type" (with a status process), the "Filter" ("All objects" or a saved view) and the "Period", then click "Show".
How the funnel is calculated:
It takes objects created during the period. Their number is "Created in the period".
Stages are the process statuses in order, except cancelled ones ("Lost", "Cancelled").
An object reached a stage if it was in that stage or in any later stage. If a deal was moved from "New" straight to "Proposal", it still counts as having reached "Qualified": skipping a stage doesn't lose it.
Column | What it means |
|---|---|
"Stage" | A process status |
"Reached" | How many objects reached the stage or went further |
"Were in the stage" | How many objects were in exactly this status |
"From previous" | The share that reached it out of those that reached the previous stage |
"From first" | The share that reached it out of the first stage |
"Median transition time" | How long it usually takes from entering the previous stage to entering this one |
Under the table is a summary of the period's objects: how many are now completed, cancelled and still in progress.
Sums. In the "Sum" list, choose a "Number", "Integer" or "Money" field, for example the deal amount. The funnel shows the sum for those that reached each stage, for all objects in the period and for the outcomes. The field's current value is used. Money in different currencies isn't converted: the sum is shown separately for each currency.
The transition history is kept for 12 months: for older objects only the current status is taken into account.
Burndown
The "Burndown" tab shows how much work is left on each day of the period — for example, how many sprint tasks are still open. Choose the "Type", the "Filter" ("All objects" or a view, for example "Current sprint tasks"), the "From" and "To" dates (no more than 366 days) and what to "Measure": the "Amount" of objects or the sum of a number field (for example, estimates in hours or story points). Click "Show".
"Remaining" — objects in the selection that weren't completed or cancelled by the end of the day. Today is calculated as of the current moment; future days show only the ideal line.
The ideal line runs from the remaining amount at the start of the period to zero on the last day.
The "Ideal line by working days" option is on by default: the line goes down only on working days and stays flat on days off and holidays. Working days come from the workspace's business hours (see below); if they aren't set up, working days are Monday–Friday, and the report says so. Uncheck the option to make the line go down every day.
The selection uses current data: if a task was moved to another sprint, it disappears from the previous sprint's report for all days.
Day boundaries follow your browser's time zone.
Time in status
On the "Time in status" tab, choose the "Type" and the "Period" (7, 30 or 90 days, a year or "Custom dates", no longer than 366 days) and click "Show". The report is available for types that have statuses.
The report takes entries into a status during the period and shows for each status:
Column | What it means |
|---|---|
"Entered" | How many times objects entered the status during the period |
"Left" | How many of them have already left |
"Still in status" | How many of those that entered haven't left yet |
"Average", "Median", "90%", "Longest" | The duration of completed stays. "90%" means 9 out of 10 stays were no longer than this |
"Now" | How many objects are in the status right now and how long they've been in it on average |
Duration is calendar time until the next transition, even if that happened after the period. Above the table is a chart of the median by status.
The same history for a single object is in its card, in the "Statuses" block: how long the object spent in each status and how many times it returned there.
SLA: deadlines in statuses
An SLA is how long an object may stay in a status. For example, a request no more than 4 business hours in "New", a ticket no more than 2 days in "Pending approval". If the object doesn't leave the status in time, Flow records a breach.
How to set an SLA
Type settings → the "Process and statuses" tab → the "Deadlines (SLA)" block → the "SLA" button:
Field | What to enter |
|---|---|
"Status" | The status in which the deadline runs |
"Deadline" | A number and a unit: minutes, hours or days |
"In business time" | The deadline runs only during the workspace's working hours; the unit can only be hours or minutes |
"Key" | The SLA's name in reports, for example |
An SLA is part of the type's process, so after changing it you need to publish the process. See Flow: statuses and the process editor.
How the deadline is calculated
The deadline starts when the object enters the status. If the object leaves the status before the deadline, the SLA is met. If not, a breach is recorded at the deadline.
A breach for one entry is recorded once and doesn't change afterwards, even if the process or the calendar is changed later.
If the object returns to the status, that's a new entry with a new deadline.
Deadlines don't run in the archive. After restoring, the deadline continues to count from the original entry into the status; one that has already passed is recorded immediately.
A "business time" deadline runs only during the working intervals of the workspace calendar. If the object entered the status outside business hours, the countdown starts at the nearest working interval.
Where to see SLAs
The object card, the "Deadlines (SLA)" block: running deadlines with a countdown and breached ones marked "breached".
"Reports" → "SLA": choose a type and a period. A table for each SLA and status: "Deadline", "Entered", "On time", "Breached", "Running" and "On time, share" = "On time" / ("On time" + "Breached"); running deadlines without a breach aren't included in the share. Below is "Breaches in period": object, SLA, status, "Deadline was", "Breached", "Left status". If there are several SLAs, the list is filtered by one.
If the type's process has no SLAs, the report tells you where to set them.
Time tracking
The "Time tracking" tab sums up the time entries members log in object cards (with the timer or manually). Choose the "Period" (or custom "From" and "To" dates), "Group by" — "By person", "By object" or 'By relation "…"' (for example, task time by project), "Billing" — "All time", "Billable" or "Non-billable", and the "Type" — then click "Show".
Above the table is the total: overall time, billable time and the number of entries.
Only time on objects you can see is counted. An entry belongs to the day the work started.
If there are very many groups, the 1000 groups with the most time are shown; the total covers all of them.
The "CSV" button downloads the entries themselves for the period, up to 50,000 entries.
How to log time and who can edit entries is described in Flow: time tracking.
Workspace business hours
Business hours (the business calendar) define when "business time" deadlines run in the workspace. Settings → the "Business hours" tab. Anyone with permission to manage the workspace can change the calendar.
Block | What to set |
|---|---|
"Time zone" | An IANA time zone, for example |
"Working hours" | For each day of the week — up to 4 intervals, for example 09:00–13:00 and 14:00–18:00; the end of the day is 24:00. A day without intervals is a day off. "Apply to all weekdays" copies Monday to Tuesday–Friday |
"Days off and holidays" | Individual dates when no one works |
Until you set up your own calendar, the standard one applies: Monday–Friday, 09:00–18:00 UTC. Above the form you see how many working hours per week you get.
After saving, the deadlines of running "business time" SLAs are recalculated in the background using the new calendar. Breaches already recorded don't change.
Business hours affect SLAs marked "In business time" and the burndown ideal line by working days. Other SLAs, deadline reminders and the "Time in status" report use calendar time. Working Saturdays (a working day that is normally a day off) and calendars per team or type aren't available yet.
What's next
Flow: the object card — deadlines and statuses of a single object.
Flow: table, board, calendar and filters — views you can use as a tile filter.
Flow: time tracking — the timer and time entries.
Flow API: reports, SLA and business calendar — the same data through the API.
ความคิดเห็น