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 * blended hourly rate from the customer-uploaded spreadsheet introduced last release.
Bloomfilter now displays cost breakdown by project’s phase of development, with the phases adding up to the subtotal for the type of cost (Build, Run, Maintain)
Added a tool tip to summarize calculation in simple terms for user.
Removed inactive DORA metrics from view. Previously the app was displaying common DORA metric fields, but there were no corresponding values being displayed (thank you, Andrew!)
Cycle time chart now lists cycles in descending chronological order.
The header was updated to include a housekeeping area for settings, legal notices, and logging out.
XLS template is now pre-filled with projects for customer.
Removed Active Sprint from setup flow.
Fixed a bug that made the Cycle Time chart disappear for users when the standard deviation for chart data was 0 (no chart was being returned).
“Add comment” now submits user-posted data to the back-end of Bloomfilter (NOTE: this does NOT add comments to Jira instance).
Limited look-back period for integration to the last twelve months. Was previously pulling from entire corpus of historical data.
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.
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.