Agile Manager Dashboards
Published on November 7, 2026
Agile Manager
Agile Manager Dashboards and Reports Guide
| This guide explains the 4 Agile Manager dashboards and the 24 reports behind them. All data comes from Agile Manager records: Stories, Tasks, Issues, Sprints, Epics, Releases, Test Cases and Test Results. |
How to Use This Guide
- Dashboards are in the Agile Manager Dashboards folder. Reports are in the Agile Manager Reports folder.
- Click any chart on a dashboard to open its report and see the records behind it.
- Dashboards show the last refresh time at the top. Use Refresh to update them.
- "Open" means not Complete or Cancelled. For Issues, "open" also excludes As Designed, Duplicate and Unable to Reproduce.
Which Dashboard Should I Use?
| Dashboard | Best for | Typical audience | When to check |
| AM - Daily Progress | Today's work, blockers and QA flow | Developers, QA, Scrum Master | Daily stand-up |
| AM - Sprint and Release Health | Capacity, velocity, release readiness | Scrum Master, Project Manager | Sprint planning and review |
| AM - Quality and Testing | Defects and test coverage | QA, Dev Leads | Daily during test cycles |
| AM - Executive View | Portfolio status and risk | Leadership, Sponsors | Weekly |
1. AM - Daily Progress
| Purpose: a stand-up view of where work stands now and what needs attention. |
| Widget | What it shows | How to read it | Report |
| Active Sprint Stories by Status | Count of stories in the active sprint, split by status | A long Blocked or New bar means the sprint is at risk | Active Sprint Stories by Status |
| Open Work by Dev Owner | Open Dev LOE per developer, stacked by story status | Tall bars mean heavy load. Compare across owners to balance work | Open Work by Dev Owner |
| QA and UAT Pipeline | Stories moving through testing stages | A wide stage means a queue. Watch Ready for QA and Ready for UAT | QA and UAT Pipeline |
| Open Issues by Severity | Open issues grouped by severity | Focus on the 1-Blocker and 2-Critical slices first | Open Issues by Severity |
| Tasks by Owner and Status | Open tasks per owner, stacked by status | Shows who has work in progress and who is blocked | Tasks by Owner and Status |
2. AM - Sprint and Release Health
| Purpose: planning and decision-making. Is the sprint realistic, and is the release on track? |
| Widget | What it shows | How to read it | Report |
| Sprint Capacity vs Load | Dev Capacity, Dev Velocity, QA Capacity and Qa Velocity per sprint | Where load is above capacity, the sprint is over-committed | Sprint Capacity vs Load |
| Active Sprint Timeline | Days remaining in the active sprint | Compare days left with open work | Active Sprint Timeline |
| Velocity by Sprint | Dev LOE of completed stories per sprint, as a line | A rising line is improving delivery. A drop needs a conversation | Velocity by Sprint (Completed Dev LOE) |
| Release Readiness by Status | Story status mix for each release as a 100% bar | A release with a large Complete share is closer to ready | Release Readiness by Status |
| Epic Progress | Closed stories against total stories per epic | A big gap between the two bars means an epic is far from done | Epic Progress |
| Release Timeline | Releases grouped by status | Shows how many releases are in each stage | Release Timeline |
3. AM - Quality and Testing
| Purpose: show product quality, defect patterns and test progress. |
| Widget | What it shows | How to read it | Report |
| Test Coverage by Story Status | Passed, Failed, Blocked and Untested test case counts by story status | Many Untested cases on stories nearing release is a risk | Test Coverage by Story Status |
| Defects by Root Cause | Issue count per root cause | The tallest bar is the most common source of defects | Defects by Root Cause |
| Defects by Type and Component | Issues by defect type, stacked by component | Shows which components produce which kinds of defects | Defects by Type and Component |
| Defects Detected by Month | Issues by month detected | A rising line means more defects are being found or introduced | Defects Detected by Month |
| Test Cases by Current Result | Active test cases by latest result | Shows overall pass health | Test Cases by Current Result |
| Test Results by Sprint and Status | Test results per sprint, stacked by status | Compares test outcomes across sprints | Test Results by Sprint and Status |
4. AM - Executive View
| Purpose: a short, high-level view for leadership. |
| Widget | What it shows | How to read it | Report |
| Stories by Project and Status | Stories per project, stacked by status | Compare progress across projects | Stories by Project and Status |
| Release Readiness by Status | Status mix per release | Which releases are closest to done | Release Readiness by Status |
| Defects by Root Cause | Issue count per root cause | Where quality problems originate | Defects by Root Cause |
| Epic Progress | Closed against total stories per epic | Which epics are behind | Epic Progress |
Report Reference
| Each report lives in the Agile Manager Reports folder. The "Used on" column shows where a report appears as a widget. Reports marked "Folder only" are lists you open directly. |
Daily Progress Reports
| Report | What it shows | Filters | Grouped by | Used on |
| Active Sprint Stories by Status | Stories in the active sprint with owner, due date and Dev LOE | In Active Sprint = true | Status | Daily Progress |
| Blocked Stories | Blocked stories with status notes and sprint, sorted by priority | Status = Blocked | None | Folder only |
| Open Work by Dev Owner | Open stories with Dev LOE | Status is not Complete or Cancelled | Dev Owner, then Status | Daily Progress |
| Overdue Stories | Stories past due date, oldest first | Due Date before today, not Complete or Cancelled | None | Folder only |
| QA and UAT Pipeline | Stories in Dev Complete through UAT Complete stages, with QA owner | Status is in the QA and UAT stages | Status | Daily Progress |
| Open Issues by Severity | Open issues with priority and age | Status is not a closed status | Severity, then Priority | Daily Progress |
| Overdue Tasks | Overdue tasks with owner, story, days past due and remaining LOE | Overdue = true | None | Folder only |
| Tasks by Owner and Status | Open tasks with remaining LOE | Status is not Complete or Cancelled | Dev Owner, then Status | Daily Progress |
Sprint and Release Reports
| Report | What it shows | Filters | Grouped by | Used on |
| Sprint Capacity vs Load | Dev and QA capacity and velocity per sprint | None | Sprint name | Sprint and Release Health |
| Active Sprint Timeline | Start and end dates, days remaining, % days passed, story and issue counts | Is Active = true | Sprint name | Sprint and Release Health |
| Velocity by Sprint (Completed Dev LOE) | Dev LOE of completed stories | Status = Complete | Sprint | Sprint and Release Health |
| Release Readiness by Status | Stories per release by status | None | Release, then Status | Sprint and Release Health, Executive View |
| Epic Progress | Total stories, closed stories, blocked stories and % complete | None | Epic name | Sprint and Release Health, Executive View |
| Release Timeline | Release dates, days remaining and % days passed | None | Release status | Sprint and Release Health |
Quality and Testing Reports
| Report | What it shows | Filters | Grouped by | Used on |
| Test Coverage by Story Status | Test case totals, passed, failed, blocked and untested | Stories with at least one test case | Story status | Quality and Testing |
| Defects by Root Cause | Issues with status and severity | None | Root Cause | Quality and Testing, Executive View |
| Defects by Type and Component | Issues by type and component | None | Defect Type, then Component | Quality and Testing |
| Open Issue Aging | Open issues with owner, detected date and age, oldest first | Status is not a closed status | None | Folder only |
| Reopened Issues | Issues reopened at least once, most reopened first | Reopened Count greater than 0 | None | Folder only |
| Defects Detected by Month | Issues by detected date | None | Detected Date (month) | Quality and Testing |
| Test Cases by Current Result | Active test cases by latest result | Status = Active | Current Test Result Status | Quality and Testing |
| Test Results by Sprint and Status | Test results per sprint | None | Sprint, then Status | Quality and Testing |
Executive Reports
| Report | What it shows | Filters | Grouped by | Used on |
| Stories by Project and Status | Stories across projects | None | Project, then Status | Executive View |
| Open P1/P2 Issues | Open P1 and P2 issues with severity, age and owner, oldest first | Priority is P1 or P2, status is not closed | None | Folder only |
Tips for Everyday Use
| Filter before you read. Add a project or sprint filter at the top of a dashboard. It narrows every widget at once. | Use the folder-only lists in stand-up. Blocked Stories, Overdue Stories and Overdue Tasks answer "what do we need to unblock today?". | Check Open Issue Aging weekly. Old open issues are a common release risk. | Watch Reopened Issues. Frequent reopens usually point to weak fixes or unclear requirements. | Drill down. Click a chart bar to open the report with the matching records. | Subscribe. Open a dashboard and choose Subscribe for a scheduled email, for example every weekday morning. |
Things to Know
| Owner fields (Dev Owner, QA Owner) are Contacts, not Users, so "My" filters do not work. Filter by owner name instead. | Sprint Capacity vs Load treats Dev Velocity and Qa Velocity as the planned load for the sprint. Confirm this matches how your team uses those fields. | Dashboards show data as of their last refresh. Refresh before a meeting. | Dashboards run as one specified user, so everyone sees the same data regardless of their own record access. |
Glossary
| Term | Meaning |
| LOE | Level of effort, usually in hours or points as your team defines it. |
| Dev Capacity and QA Capacity | The effort available for development or testing in a sprint. |
| Velocity | Effort delivered in a sprint. |
| Root Cause | The origin of a defect, for example requirements, design or code. |
| Reopened Count | How many times an issue was closed and then reopened. |
Knowledge Article Number: KA-00497