📣 Agile Charts level up: Epic estimate forecasting, JQL Epic filtering, “Done” status configuration

[#1]

Hey Atlassian Community! 👋

We're thrilled to announce major updates from Broken Build for our Agile reporting suite! The latest releases bring powerful new forecasting capabilities, smarter filtering, and workflow improvements that make tracking and predicting delivery dates easier than ever.

These updates span across Agile Burnup Burndown Charts 2.3, Agile Cycle Time Chart 2.3, and the comprehensive bundle Agile Reports & Gadgets 8.3 (which includes both apps plus Agile Velocity Charts).

✨ Key Highlights:

• Epic estimate forecasting – Predict timelines from Epic-level estimates across three initiative stages (pre-launch, in-progress, near completion)

• JQL Epic filtering – Dynamically focus on specific Epics using custom JQL queries

• Simplified “Done” status configuration – Merged duplicate status names for easier setup

• CSV data export – Export Cycle Time data for external analysis

• Sprint rollover improvements – Better alignment with sprint filters in Velocity charts

• Critical bug fixes – Resolved chart freezing and timezone calculation issues

📊 Available in: Agile Burnup Burndown Charts, Agile Cycle Time Chart, Agile Reports & Gadgets

Epic forecasting, smarter filtering, cleaner configuration, and critical fixes - these updates give you the tools to predict and track delivery at any initiative stage. Let's dive in! 🚀

What's new across the Agile charts

1. 📈 Forecast delivery with Epic estimates

The headline feature: probabilistic forecasting using Epic estimates. Now you can predict delivery timelines even when Stories aren't fully broken down or estimated.

The problem it solves: Early in any initiative, teams work with rough Epic-level estimates - t-shirt sizes or Epic Story Points, but Stories are incomplete. Until now, Jira lacked a flexible tool to turn these high-level estimates into reliable forecasts.

How it works across initiative stages:

📍 Before the initiative begins

• Epics are estimated, Stories are partially defined (not estimated)

• No completed work yet = no historical velocity

• Set Remaining work: Epic estimate + enable alternative throughput to model expected team capacity

• Result: Cone of uncertainty showing Epic delivery forecasts based on assumed throughput

📍 After work begins - some progress made

• Epics adjusted as things evolve, Stories mostly decomposed and estimated

• Some items are completed, but the velocity is not yet stable

• Configure Remaining work: Epic estimate + use main or alternative throughput

• Result: Hybrid forecasts blending Epic estimates with emerging completion data

📍 Nearing completion - scope stabilizing

• All Stories decomposed and estimated, more than half completed

• Throughput is stable and reliable

• Switch to Remaining work: Auto to derive work from child Stories automatically

• Result: High-confidence forecasts based on actual story data and proven throughput

💡 Pro tip: Use this during portfolio planning and roadmap discussions. Test resource-allocation scenarios with alternative throughputs, explore scope changes at the Epic level, and provide stakeholders with realistic delivery windows - all before committing to detailed breakdowns.

Configuration options: Select Epics directly as your data source, or pick any data source (board, filter, project) and filter by specific Epics.

Across all stages, this approach lets you evolve smoothly from Epic-level forecasting (when very little is known) to story-level forecasting (when most details are known), without changing tools or concepts - just by adjusting how you configure Remaining work and throughput.

📊 Available in: Agile Burnup Burndown Charts, Agile Reports & Gadgets

☁️ Cloud and Data Center

2. 🔍 JQL Epic filter - dynamic, query-based Epic targeting

Filter your charts to show specific Epics using custom JQL conditions.

Use cases:

• Show only Epics from a specific project

• Filter by Program Increment using a custom field

• Target Epics matching labels, components, or any JQL criteria

Instead of manually selecting Epics one by one, write a query that automatically includes the right ones. Surgical precision for your data sources.

📊 Available in: Agile Burnup Burndown Charts, Agile Cycle Time Chart, Agile Reports & Gadgets

☁️ Cloud and Data Center

3. ✅ One "Done" option instead of dozens - status confusion solved

If your Jira instance has dozens of "Done" statuses and you've struggled to figure out which belongs to which board, this fix is for you.

What changed: The custom Done status dropdown now shows just one "Done" or "In Progress" option. Behind the scenes, the chart intelligently maps to the correct underlying status for each board.

This streamlines configuration in large Jira instances with complex workflows across multiple teams.

💡 Pro tip: Huge time-saver when building cross-team dashboards. No more auditing, which "Done" status maps where - the chart handles it. Select "Done" and move on.

📊 Available in: Agile Burnup Burndown Charts, Agile Cycle Time Chart, Agile Reports & Gadgets

☁️ Cloud and Data Center

4. 📤 Export Cycle Time data to CSV

Highly requested: CSV export for Cycle Time charts (Histogram, Trend, Time in Status).

Why export?

• Analyze in Excel, Google Sheets, or BI tools

• Create custom visualizations or executive reports

• Integrate metrics into external dashboards

• Archive data for audits or compliance

💡 Pro tip: Build custom trend analysis across long time periods. Combine data from multiple quarters, create pivot tables, or build advanced charts for leadership presentations.

📊 Available in: Agile Cycle Time Chart, Agile Reports & Gadgets

☁️ Cloud and Data Center

5. 🎯 Velocity rollover now respects sprint filters

When you filter sprints in Velocity charts, Rollover metrics now calculate based on the filtered sprint order (not the unfiltered sequence).

This ensures rollover accurately reflects the sprint sequence you're analyzing - critical when you exclude outlier or experimental sprints.

💡 Pro tip: Use this when analyzing specific sprint ranges or excluding holiday sprints with reduced capacity. Rollover now reflects only your filtered view, making velocity trends more meaningful.

📊 Available in: Agile Reports & Gadgets (Velocity charts)

☁️ Cloud and Data Center

6. 🐛 Bug fixes - better performance and accuracy

Two critical fixes:

• Chart freezing resolved – Burndown and Burnup charts now load smoothly, even with large datasets

• Timezone scoping corrected – Timezone settings from work schedules now apply only to Cycle Time charts, preventing unintended impacts elsewhere

📊 Available in: Agile Reports & Gadgets

☁️ Cloud and Data Center

🔗 See it in action: explore interactive chart examples

Want to see these updates in real Jira environments? We've built a library of interactive chart examples you can explore right in your browser - no login required.

🛠️ Check out examples like:

• Epic burnup chart

• Initiative burndown chart

• Epic Time in Status chart

• Epic progress report

📚 We're constantly adding new scenarios - the library keeps growing!

👉 Browse all interactive examples

🚀 Upgrade today and level up your dashboards

These updates to Agile Burnup Burndown Charts, Agile Cycle Time Chart, and Agile Reports & Gadgets represent a major leap in how teams forecast, track, and optimize Agile workflows. Epic-based forecasting alone changes the game for portfolio planning - now you can predict with confidence at every stage, from rough estimates to detailed execution. 🎉

Add in JQL Epic filtering, simplified status configuration, CSV exports, and critical performance fixes, and you've got a toolkit that truly adapts to your needs.

🙌 Get started:

1. 🛒 Try the standalone apps on Atlassian Marketplace – Free trials available:

• Agile Burnup Burndown Charts

• Agile Cycle Time Chart

• Agile Velocity Charts

2. 💼 Explore the full bundle for complete Agile reporting across your teams

• Agile Reports & Gadgets

3. 📊 Add these gadgets to your Jira dashboards

Happy dashboarding! We're excited to see how these updates transform your planning and delivery. 📈✨

🎯 See charts in action with our interactive examples

💬 Have questions or feedback? Contact support

—
The Broken Build Team