Analytics and reporting
Every workspace has built-in analytics tuned to that role. All analytics are scoped to what you can see: admins see the whole organisation, everyone else sees only their apps (and developers and testers only their own work).
QA Sync doesn’t export reports or connect to BI tools; the charts below are the reporting surface.
Overview
Section titled “Overview”The Overview tab opens with headline cards (Apps, Tasks In Flight, Blocked Items, Overdue Items, Pending QA, Ready For Release), then groups metrics into sections:
| Section | Contents |
|---|---|
| Health Snapshot | Delivery Health (average cycle and lead time, blocked time %, workload balance), QA Health (passed, failed, in testing, needs retest, QA throughput, average retest count), Release Health (ready, at-risk, approved and overridden releases, release frequency over 30 days, average release confidence and dependency risk), People & Intake (testers, developers, pending requests). |
| Planning & QA Mix | Tasks by Priority, Tasks by Risk, QA Status Breakdown, QA Severity Breakdown, Average Bug Count by Module and by App. |
| Trend Signals | Stage Aging, Throughput Trend, Release Confidence, Sprint Velocity. |
| Operational Pressure | Workload Balance and Bottlenecks. |
Analytics
Section titled “Analytics”The Analytics tab goes deeper:
| Chart | Shows |
|---|---|
| Throughput Trend | Production completions by week for the last six weeks. |
| Stage Aging | Average hours work sits in each stage. |
| Workflow Heatmap | Stage concentration by contributor, so congestion stands out. |
| Workload Distribution | Active load per contributor. |
| Workload Balance | Active load, overdue pressure and QA loop history per contributor, labelled Balanced or Overloaded. |
| Release Confidence | Confidence across releases. |
| Bottlenecks / Bottleneck Highlights | Highest-delay items, from workflow age and repeated QA failures, with a suggested action. |
Product Manager
Section titled “Product Manager”| Tab | Charts |
|---|---|
| Summary cards | Roadmap %, Release Health, Sprint Complete %, Scope Creep %, Dependency Risk. |
| Portfolio | App Portfolio, Priority Distribution, App Progress, Release Health, Release Confidence, Dependency Risks. |
| Roadmap | Roadmap Timeline, Milestone Progress, Milestone Risk, Sprint Velocity, Sprint Burnup, Sprint Burndown, Scope Creep, Roadmap Risks. |
| Release | Release Health, Dependency Risk, Release Bottlenecks. |
Developer
Section titled “Developer”The History tab includes: Throughput Trend (your production completions over six weeks), Status Mix (your work by stage), Risk Areas (modules with the most blocked or aging work in your queue), Personal Workload, and Actionable Bottlenecks.
Tester
Section titled “Tester”The Health tab includes: Queue Load, Pass Rate %, Fail Rate %, Avg Bugs, Retest Cycles, Severity Mix, Hotspot Modules, QA Throughput (runs over six weeks), Queue Bottlenecks, and a QA Health Snapshot.
UI Designer, Client and Viewer
Section titled “UI Designer, Client and Viewer”Summary cards (Apps Needing Attention, Release Health, Roadmap Progress, Visible Roadmap Items), plus App Portfolio, App Progress, Release Health, Release Confidence, Roadmap Snapshot, Milestone Progress, Milestone Risk, Sprint Burnup and Sprint Burndown.
Key metrics explained
Section titled “Key metrics explained”| Metric | Meaning |
|---|---|
| Cycle time | Hours from starting work to finishing it. |
| Lead time | Hours from creating an item to finishing it. |
| Blocked time % | Share of active time items spend blocked. |
| Release health | Score per release version from readiness, blockers and QA pressure. |
| Release confidence | Score per release version from readiness, blockers and approvals. |
| Dependency risk | Pressure from incomplete dependencies, per release or overall. |
| Milestone progress | Shipped tasks as a share of tasks linked to the milestone. |
| Milestone risk | Blend of blockers, overdue work and aging active tasks. |
| Sprint velocity | Completed story points per sprint. |
| Burnup / burndown | Delivered and remaining story points per sprint. |
| Scope creep | Share of sprint scope added after the sprint started. |
| QA pass / fail rate | Share of finished QA runs that passed or failed. |
| Retest cycles | QA runs that were retests of failed or blocked work. |
Why is my chart empty?
Section titled “Why is my chart empty?”Charts fill in only when the data behind them exists:
| Chart | Needs |
|---|---|
| Roadmap, milestone charts | Items linked to milestones, or release versions with due dates. |
| Sprint charts | Tasks linked to sprints, with story points. |
| Release health and confidence | Release versions on tasks. |
| Priority distribution | Priorities on items. |
| QA charts | Finished QA runs. |
| Throughput | Items reaching Production over time. |
Admins set these fields on apps, modules, submodules and tasks. See Planning fields.