Vasyl Krokha _Broken Build_ Atlassian Partner

The Created vs Resolved report answers one of the most common questions in project management: is work leaving the backlog as fast as it enters? For single-board, single-question scenarios, the native Jira report handles this well. The trouble starts when you need to know why the gap exists – or when your scope extends…

Every team that ships software faces the same running question: is work arriving faster than we can finish it? A Created vs. Resolved chart answers that directly – it tracks how many work items enter a queue versus how many leave it over a given period. When the two lines diverge, something needs to change. Agile Created…

Agile WIP Charts adds WIP aging and flow diagnostic charts to Jira Cloud. The WIP Aging chart – the app's core view – shows how long each in-progress issue has spent in each workflow status, so scrum masters and delivery managers can spot aging work during standup and daily triage. You know the moment in standup: someone…

You can report on a Jira project in more than one way. You can open the Reports tab and read a predefined report. You can build a Jira dashboard from gadgets and saved filters. Both are valid Jira workflows. The trouble starts when the question gets bigger than one report. If the team needs to explain delivery pace, scope…

Jira components are project-scoped. That works fine for a single project – but once multiple projects share the same functional areas like "Authentication" or "Payments API", keeping them in sync becomes a maintenance problem. Each project gets its own copy, names drift over time, and cross-project reporting turns into a…

Agile Reports & Gadgets brings 8 chart families – Velocity, Cycle Time, Burnup/Burndown, Monte Carlo, Throughput, Cumulative Flow, Created vs Resolved, and WIP – along with 30+ delivery metrics and issue-view panels into one Jira app. Teams use it to track sprint performance, forecast delivery dates, and surface flow…

Jira components are useful until the list gets long enough that the right component is hard to find, hard to explain, or hard to use consistently on an issue. The core idea behind Subcomponents for Jira Cloud is to keep Jira's native components, but organize them as a component hierarchy: admins can add existing or new…

Subcomponents for Jira Cloud was migrated to Atlassian Forge in 4.0.0, bringing enhanced security for users. Forge also allowed us to introduce features that were not feasible before: automated migration with JCMA for users moving from Jira Data Center to Jira Cloud, and feature parity between Data Center and Cloud (a…

A delayed Jira issue rarely explains itself. You can see that a ticket is late, or that cycle time is rising, but the next question is usually harder: is this specific work item actually at risk, and what happened in its workflow before it got here? Agile Cycle Time Charts 2.4 brings that investigation into the Jira issue…

If you run Monte Carlo forecasts in Jira, you already know the pitch: a confidence range instead of a single optimistic date. You also know the two places it tends to stall before stakeholders trust it. Wall one is the estimation field. Teams that plan in hours and days, not story points, get asked to translate their real…

Kanban teams need a consolidated view of completed work over time to track velocity trends, compare performance across one or multiple teams, and spot changes in delivery stability. Without this visibility, teams struggle to answer critical questions: "How much work do we typically complete each week?" "Is our delivery…

Delivery problems don't announce themselves. Backlog grows quietly. Work stays in progress longer than anyone intended. By the time the slowdown becomes obvious, the window to course-correct is already closing. That's exactly the gap Agile Reports & Gadgets 9.0 is designed to close. This release introduces two new chart…

Some problems only become visible after the damage is already done. A work item quietly stalls in Ready for Testing for three weeks. Code review times creep from one day to three. A handful of items sit blocked for months while the team keeps pushing forward – unaware. Reactive discovery is the enemy of flow. That's…

Modern delivery excellence depends on two fundamental principles: treating your delivery system as a continuous flow and driving improvement through data-informed decisions. Think of your workflow as a network of interconnected pipelines. Work items flow through these channels, and throughput becomes your essential…

Agile teams often struggle to see how individual contributors perform across sprints. Without per-user metrics, you're left guessing who's overloaded, who's consistently undercommitting, and where bottlenecks actually occur. The result? Unbalanced workloads, missed deadlines, and sprint planning based on gut feeling rather…

A burnup chart tracks two things simultaneously: how much work your team has completed and how the total scope has evolved. Unlike a burndown chart, which only shows remaining work, a burnup makes scope changes visible the moment they occur. Jira's native burnup chart covers the basics, displaying Work Scope, Scope…

A burndown chart for Jira answers one question every Agile team asks during a sprint: Are we going to finish on time? By plotting remaining work against time, it gives teams an early signal when scope or pace is drifting, before the end of the sprint makes it obvious. This guide covers how Jira's built-in burndown chart…

Every agile team eventually hits the same wall: you have metrics, but not a system. You can see velocity, but not flow. You can measure output, but not predictability. Individual charts answer individual questions - but they rarely tell the full story. That's exactly what Broken Build set out to fix with Agile Reports &…

Hey Atlassian Community! 👋 We're thrilled to announce that Agile Reports & Gadgets has earned the Runs on Atlassian badge - a significant milestone that reinforces our commitment to data security and enterprise-grade protection. About Agile Reports and Gadgets Agile Reports & Gadgets is our comprehensive reporting bundle…

Hey Atlassian Community! We're excited to announce the release of Agile Velocity Chart 7.0, launched on December 24, 2025 – a major app and user experience upgrade from Broken Build that reshapes how you track and analyze velocity. This release also marks our achievement of the Runs on Atlassian badge by moving the app to…

Hi everyone! 👋 I’m curious to learn more about how teams and practitioners in the Atlassian ecosystem discover the professional information that actually influences their decisions - whether it’s tooling, reporting practices, delivery approaches, or process improvements. There’s so much content out there (blogs, YouTube…

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…

Hey Atlassian Community! 👋 At Broken Build, we're constantly evolving our suite of tools to tackle the core challenges facing Agile teams. We recently launched Agile Cumulative Flow Charts to help you track flow stability with Arrival Rate, Departure Rate (Throughput), and WIP to stay aligned with health metrics. Now,…

🚀 Update (Released): Agile WIP Charts is now live and available on the Atlassian Marketplace. Read the full release announcement here: 👉 https://community.atlassian.com/forums/App-Central-articles/Agile-WIP-Charts-1-0-From-invisible-bottlenecks-to-real-time/ba-p/3217413#M15613 Hey Atlassian Community! 👋 At Broken Build,…

🚀 Update (Released): Agile Throughput Charts is now live and available on the Atlassian Marketplace. Read the full release announcement here: 👉 https://community.atlassian.com/forums/App-Central-articles/Turn-delivery-throughput-data-into-actionable-insights-Agile/ba-p/3192357#M15165 Hey Atlassian Community! What if you…

Agile teams constantly face this challenge: work starts, effort is invested, but nobody can confidently answer "how long will this actually take?" Without visibility into delivery speed, planning becomes guesswork, bottlenecks stay hidden, and stakeholder conversations rely on assumptions rather than data. The Cycle Time…