Agile Reports and Gadgets for Advanced Agile Reporting in Jira and Confluence

Track individual, team, and cross-team progress with advanced velocity and benchmarking charts
Predict delivery timelines for Epics, Features, Initiatives, and Releases, using past performance, what-if, and backlog growth rate scenarios
Refine charts with filters for epics, releases, or custom JQL
Generate shareable Agile charts as Jira dashboard gadgets or widgets, global reports, or within individual Jira projects

Try it free

Schedule a demo

Plan, track, and report with Agile Reports and Gadgets

Choose Scrum, Kanban boards, or their combination as a data source.
Track individual, team, and cross-team progress. Inspect your sprints with 10 advanced sprint metrics.
Use sprint breakdowns by issue type, priority, assignee, and more. Filter velocity by epics, releases, bugs, stories, or custom JQL for in-depth sprint analysis.

Analyze active, past, and future sprints. Predict delivery dates using past performance, what-if, and backlog growth rate scenarios.
Plan, forecast, and track the progress of Releases, Epics (Features), and any entity above, such as Initiatives, Program Epics, Themes, and others, along with custom JQL.

Employ ready-to-use charts and start using our apps with just a few clicks.
Easily group boards and create board sets.
Set the charts' height to match your dashboard.

Everything you need for Agile reporting in Jira

What-if scenarios:

Identify delivery dates under optimistic, realistic, and pessimistic velocity scenarios
Specify the date and find out the team velocity needed to meet the deadline
Input a custom velocity value and estimate the delivery date
Get a forecast for the custom size of the remaining work scope
Check how scope growth may impact the delivery timelines

Instantly access a detailed sprint or interval report (for Kanban or JQL charts) to analyze the scope issue by issue without leaving your Jira Dashboard or the context of your Jira project.

Build any chart using:

any Jira numeric field (e.g., “Feature Points” or “Epic Points” custom field)
“Story Points” and “Story Point Estimate” fields for company-managed and team-managed Jira projects, respectively. Combine both types of Jira projects on cross-team charts
an integrated approach that accounts for “Time Spent” and “Remaining Time” fields for accurate chart calculations

Review broader data trends: analyze chart data for sprints or intervals grouped by months or quarters.

Apply User Preferences to view or hide data on your velocity chart without affecting the chart’s appearance for other users. Edit rights for a Jira dashboard are not required.

By analyzing relative metrics you can:

evaluate the Say:Do ratio
adopt a unified approach to compare performance of multiple teams
track the progress of team improvement over time

Set goals or thresholds with target lines.

Teams differ by their Definition of Done - this becomes crucial when building cross-team velocity charts.

Decide which statuses to consider as Done for each team or use the default, where statuses from the last board column are considered Done.

Velocity Chart - often teams don’t estimate small issues, such as tiny bugs found during an active sprint. To account such Jira issues, use the default estimate
Burnup Chart - backlog items may be unestimated but you can specify default estimate for them for better forecasting

Exclude specific sprints from the velocity chart. This is useful when:

Teams sharing the same Scrum Board use distinct sprint names, such as “Team A - Sprint 1”, “Team B - Sprint 1”
You want to exclude some sprints from the chart