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.
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.