With the team ahead of plan on our roadmap, we sought to use this sprint to begin backend work that would support the new user experience of the Beta-to-GA version of Bloomfilter.
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.
Users are now able to select a date range for their Financial information about a project (current month, quarter, year; trailing three, six, and twelve months).
Added support for multiple Jira instances integrating with a single Bloomfilter org.
Bread crumb navigation has been updated so that it follows the hierarchy of the application more closely (Portfolio > Project > Current, Historical, or Financial View > Issue or Chart Details).
Removed icons next to the issues reported for a sprint. Previously we had displayed icons that were intended to help users understand the severity of the issue, but early adopter feedback indicated that the icons were causing confusion when shown in relation to issue results that didn’t seem to match the positive/negative sentiment of the results (e.g., a full sprint of work read in the backlog was getting a red/hazardous icon).
Current Sprint burn metrics were not displaying the current day’s data. This has been updated to take advantage of the fact that we should be as current as within an hour of current day, current time.
Fixed a bug that prevented tasks from being retrieved during initial integration setup in some cases.
Fixed a bug where Current Sprint data was showing a day in visualization. The first day of the sprint displayed a non-sensical set of charts as a result.
Fixed a bug where point value displayed on the burndown for the previous sprint was displayed incorrectly.
Updated the project summary view based on the number of other fixes going on at the project level during the sprint (changes elsewhere were creating an outdated summary algorithm). The information being displayed was greatly overstating values for the most recent sprint.
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.