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, we're excited to announce our next innovation: Agile Created Resolved Charts β coming soon to the Agile Reports suite!
π Join the waiting list:
Fill out the Google Form to be added to the list
Ever wondered if your team is keeping up with demand? Are new items flooding in faster than you can deliver? Created vs. Resolved Charts (sometimes called Throughput Charts) answer the fundamental question every Agile team needs to ask: Are we in balance?
Whether you're running Scrum sprints, managing Kanban workflows, handling service desk tickets, or coordinating at SAFe portfolio levels, this app gives you the visibility to keep queues under control and catch problems before they escalate.
Configure exactly how you want to measure flow through your system:
π· Chart modes:
By Period (run) view β See arrivals vs. departures per sprint, week, or day to spot capacity imbalances
Cumulative view β Track inventory growth over time and predict when backlog pressure will hit critical levels
π· Calculation options:
Define what counts as "Created" β on issue creation or when work enters a commitment gate (like "Ready for Dev")
Choose which statuses mark work as "Resolved" β all Done statuses or specific completion criteria
π· Estimation fields:
Track by Story Points, Original Estimate, Time Spent, or any custom numeric field
Or simply count items when estimation isn't used
Fine-tune your throughput analysis to match your team's rhythm:
π· Timeframe selection:
Pick preset ranges (last 10 sprints, last 30 days) or set custom date windows
Exclude active periods to avoid skewing metrics with incomplete data
π· Data grouping:
Daily grouping for Kanban teams and service desks
Weekly grouping for stable trend analysis
Monthly grouping for program or portfolio views
By Sprint grouping for Scrum teams
π· Chart types:
Line charts to visualize trends and flow patterns
Bar charts to highlight discrete intervals and compare periods
Pull throughput data from wherever your work lives:
β
Scrum or Kanban boards β track one or combine multiple boards
β
Projects and Releases β filter by specific versions and deliverables
β
Custom JQL / Saved Filters β create cross-project views, QA stage analysis, or service desk monitoring
...and more features coming your way!
The Created vs. Resolved Charts transform how you handle demand and delivery:
π Balance demand & capacity β spot when arrivals consistently outpace departures before your backlog spirals out of control
π Stabilize throughput β identify variability patterns and eliminate batching behaviors that create unpredictable delivery
π Control scope creep β watch the gap between what arrives and what ships to manage backlog pressure proactively
π Predict delivery risks β catch early warning signs of cycle-time problems and coordinate interventions before commitments slip
The result? Teams that maintain a sustainable delivery pace, stakeholders who get realistic forecasts, and leaders who can make capacity decisions based on real throughput data instead of guesswork.
Want to be the first to know when Agile Created Resolved Charts goes live?
π Join the waiting list:
Fill out the Google Form to be added to the list
Reach out to our Support team
π§ Explore more:
Book a demo to get a preview of how the app works
While you wait for Agile Created Resolved Charts, explore our existing apps designed to give your team complete visibility:
π· Individual apps:
π· Complete solution:
Agile Reports & Gadgets (Bundle) - Access the combined capabilities of our four individual apps in a single comprehensive package, including Velocity Charts, Cycle Time Charts, and Burnup Burndown Charts.
Keep your demand & capacity balanced, your entry & output stabilised, and your delivery predictable. Discover new Agile insights with Broken Build β because better visibility means better decisions.
Cheers,
The Broken Build Team π
Vasyl Krokha _Broken Build_
0 comments