Jira Enterprise Dashboard gives engineering teams a single Jira-native view of velocity, throughput, investments, and quality trends across the last 12 months.
1. What the dashboard does
The app aggregates Jira data across selected projects and renders it as four tabs: Velocity, Product, Quality, and Configure. It is intended for engineering managers and leadership teams that need cross-project visibility without exporting Jira data into spreadsheets.
- Velocity: Sprint and release story-point delivery performance.
- Product: Throughput and allocation of effort across bugs, improvements, and tasks.
- Quality: Bug volume, defect ratios, and lead-time trends.
- Configure: Shared filters and categorization rules applied to all viewers.
2. Requirements and data prerequisites
For the most accurate metrics, ensure your Jira data follows these conventions:
- Projects are company-managed Scrum projects.
- A Story Points field exists and is populated on tickets used for velocity.
- Project versions are maintained (release dates recommended when correlating by date).
- Affected Version is set on bugs you want counted as opened against releases.
- Fix Version is set on tickets you want counted as committed/completed per release.
Metrics are calculated for the rolling last 12 months.
3. How to use each tab
Velocity
- Shows committed vs completed story points for sprints and releases.
- Highlights completion rate, trend, variance, and overcommitment.
- Uses story-pointed issues only (story points must be greater than zero).
Product
- Throughput: Created vs closed ticket counts by month.
- Investments per Version: Share of closed story points by category (bug/improvement/task).
- Total Tickets: Distribution of created and closed tickets by priority.
Quality
- Opened and Closed Bugs per Version: Bug counts by priority and version.
- Defect Ratio: Bugs opened divided by improvements closed.
- Project-level views: Top projects by defect ratio and average bug lead time.
4. Configure tab (shared settings)
Configuration is global for the dashboard. When you save changes, the updated filters apply to everyone viewing the app.
- Projects: Include all projects or choose a specific set.
- Version correlation: Aggregate versions across projects by version name/number or by release date.
- Ticket categories: Map Jira issue types into Bugs & Issues, Improvements & Innovations, or Tasks / Other.
Only issue types mapped to a category are included in calculations. Use Restore Defaults to reset filters.
5. Metric interpretation notes
- Large Jira sites may take longer to load; the UI shows progress as projects and boards are processed.
- Release metrics depend on version hygiene (especially Fix Version and Affected Version usage).
- Lead time is measured in calendar days from issue creation to resolution.
- If your organization uses custom workflows, status-based completion behavior can affect counts.
6. Troubleshooting
- No velocity data: Verify story points are populated and Scrum boards/sprints are active.
- Sparse release charts: Confirm versions exist and Fix Version/Affected Version fields are used consistently.
- Unexpected category totals: Review issue-type mapping in Configure and save changes.
- Permissions gaps: Dashboard results reflect Jira data the viewing user can access.
7. Support
For help with onboarding, configuration, or troubleshooting, contact [email protected].