These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Task & Kanban Board
- Features
- Flow insights
Flow insights
Read aging, completion and workload with the history behind the numbers.
OverviewBoard Flow History×
Task & Kanban Board · Flow insights
New
Board Flow History
Board snapshots
| Snapshot number | Board | Snapshot at | Active task count | Overdue task count | Completed cycles | |
|---|---|---|---|---|---|---|
| BS-36731 | Billing improvements | 19 Oct | 9 | 9 | 60 | |
| BS-61050 | Billing improvements | 28 Oct | 39 | 11 | 220 | |
| BS-79672 | Website updates | 28 Oct | 24 | 5 | 100 | |
| BS-64819 | Website updates | 25 Oct | 26 | 11 | 210 | |
| BS-44953 | Website updates | 23 Oct | 39 | 8 | 70 |
6 of 6 records
Billing improvementsBoard snapshots · BS-36731
Snapshot at19 Oct
Active task count9
Overdue task count9
Completed cycles60
Reopened cycles150
What you can do
Complete the handoff
The move service consumes an Approved transition requests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity. Mark Applied only when the move commits. Entering Done stamps completed at and appends one Completed task events row for Task plus cycle number. An approved request with no free slot remains approved but unapplied until it can be safely retried; approval alone is not completion.
Follow up on dates
The reminder service evaluates due date in the board timezone and schedules a unique notification deliveries occurrence for the intended current owner or reviewer. Recheck the task, audience and date immediately before sending. Completed, cancelled, archived or rescheduled work suppresses an obsolete reminder. Provider acceptance and observed delivery remain separate, and an unknown result keeps its original operation key for reconciliation.
Reopen or archive
Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment cycle number and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.
Review flow
Board Owner reads board snapshots and event-based reports with their time window, timezone and definition version. Distinguish completed cycles from reopened work and unfinished aging. An empty result has no measured cycle time. Compare owners’ workload in context; task counts alone do not establish productivity. Viewer receives only the permitted board reports, and Guest has no board-wide analytics or export.
Review a reopened task fairly
A Friday completion can reopen on Monday because new work is required. Friday’s event keeps its observed owner, deadline and timing. Monday starts a new numbered cycle. Restoring archived work also rechecks the destination’s current capacity, so archiving cannot become a way to bypass a full column. Reports show the earlier completion and the reopen without rewriting either into a cleaner history.
Cycle time needs actual start and completion observations under a declared elapsed-time definition. An empty result is not zero-day delivery. Never-started work contributes to unfinished aging where appropriate, while cancelled work is not completed delivery.
Snapshots identify observation time, timezone and definition version. Compare the same reporting window and definition before interpreting change. Many small tasks and a few complex tasks cannot establish a productivity ranking. Use workload views to find blocked or overdue work and discuss its context. Follow an uncertain reminder through its retained delivery record instead of assuming an attempted message reached its recipient.
What your team sees
- Board Flow History. Open the current records for this module within your assigned role and permitted scope.
What it keeps track of
Data model- Board snapshots
- Dated board metrics derived from retained events and explicit cycle definitions.
- Task events
- Append-only task changes and completed cycle evidence.
- Tasks
- Canonical work item. One column owns the workflow position; filters and lanes never duplicate the task.
- Notification deliveries
- Observable reminder and mention delivery attempts; delivery does not approve or complete a task.
Who uses it
Permissions- Board Owner
- And permitted Viewer read board reports.
- Guest
- Has no board-wide analytics.
Set up Task & Kanban Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.