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.
Enhancements
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).
New dropdown on Financials page to filter date range for data displayed.
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).
Breadcrumb nav when user is on the issue details page within a project/sprint.
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).
Issues at right no longer display seemingly random red, yellow, and green icons.
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.
Fixes
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’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.
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.
