Changelog

Introducing new AI driven capabilities (called Bloomcast) and dynamic forecasting with Confidence Chart. We are tracking work with greater precision.

Sprint 23 saw the launch of our MVPs for The Big Summary and The Sprint Performance! We’re excited about these two new features and the direction they are taking Bloomfilter in.

We’ve previously talked about our Burn Confidence band, which measures team performance as compared to expectations in a static representation. However, the development lifecycle is constantly changing and requires teams to respond dynamically. We are excited to announce that our latest update to the Burn Confidence Band transforms the band into a dynamic forecasting tool based on a rolling sequence of burn data from past sprints.

In Sprint 22, two key features are in User Acceptance Testing (UAT): a new Summary page as the app home screen and an update to our frequently used feature, Sprint Performance.

Sprint 21 focused on two exciting features: a new Summary page that will serve as the app home screen, and an update on Sprint Performance, our most frequently used feature.

Sprint 20 found the team breaking ground on a new home page for the platform! This effort will take multiple sprints, but the payoff will be a summary view, for our customers, of the three big questions: What are we building? When will it be done? How much will it cost?

Sprint 19 is all about visualizing your past with enhanced project statistical charts. You can now track trends from up to 16 sprints ago, and with our dynamic data representation, get a more accurate view of your Cycle Time, Lead Time, and Reaction Time. Alongside these updates, we've also refined our user interface for better navigability and clarity.

We introduced valuable features like error screens, visual representation for non-working days, and enhanced security measures. We also improved the user experience when navigating between Jira boards, and upgraded Bloomfilter with Mantine 6.0 for more design flexibility.

In this update, we've revamped our Burn Commitment chart based on Early Adopter feedback for a better user experience. We've also refined data presentation to align with Jira stories. Plus, we've fortified the User and Organization models against potential pen test attacks to enhance customer security.

Users now have the ability to associate more than one active board per project in their configuration. Customers who run their dev, design and QA on different boards may now rejoice!

The first of two deployments aimed at supporting multiple active boards per project, i.e. if your Engineering and QA teams work off of different boards. While the work on that more complex feature will carry over into our next release (mid April), we shipped some minor bug fixes in the mean time.

This release includes updates to navigation, page layouts, and how we use headings/sub-headings to help the user orient to the page they are on.

Within our emerging Financials feature, we sought to introduce three blended-cost breakdowns: Build, Run and Maintain cost breakdowns. This is a calculation using dev work in each phase of development and blended hourly rate from the customer-uploaded spreadsheet introduced last release.

We are excited to introduce the new Financials page. This new view provides customers with the ability to understand development effort through the lens of cost, and the ability to break down costs between build, run, and maintain.

Released the early adopter trial program allowing prospects to connect Jira with OAuth and to see their data in Bloomfilter, fixed a few bugs and improved some UI elements.