What this does
Reports give managers factual, filterable visibility into delivery — never a performance score for any individual.
Before you begin
Reports requires the reports.view permission (Administrators by default).
Viewing a report
- Open Reports in the sidebar.
- Choose a date range (presets like This Week, This Month, Last 30 Days, or a custom range).
- Optionally narrow by project, assignee, owner, task type, priority, or release.
- Select a tab — Overview, Delivery, Workflow, Understanding, QA, Releases, or Team Workload.
Report areas
- Overview — tasks created and completed, active and blocked counts, overdue tasks, and average cycle time.
- Delivery — created vs. completed over time and current status distribution.
- Workflow — how long tasks spend in each stage, and which tasks are currently blocked and for how long.
- Understanding — how many tasks are waiting on submission, review, or are outdated, plus how long submission and review typically take.
- QA — QA cycle counts, first-pass rate, and average QA duration.
- Releases — release status counts, delayed releases, and releases completed in the selected period.
- Team Workload — each person's current open/in-progress/blocked/ready-for-QA/changes-requested/ready-for-release counts, plus what they completed in the selected period.
Definitions worth knowing
- Cycle time is the elapsed time from a task's first move into In Progress to its most recent completion — wall-clock time, not logged working hours.
- First-pass QA rate is the share of tasks whose first completed QA cycle passed, out of tasks that have at least one completed QA cycle. Tasks that don't require QA aren't counted on either side.
What reporting is not
Important
Reporting shows operational counts and timing — never an individual performance score, ranking, or rating. A task count is not a measure of how well someone is doing their job, and BriefFlow doesn't present it as one.
Common issues
A tab shows "No data for this period." Widen the date range or clear a filter that may be excluding everything — this is the correct empty state, not an error.