We’re launching two exciting improvements to how we identify and manage issues throughout Noibu: Improved Issue Titles and Closed-Fixed Issue Filtering.

Improved Issue Titles

Some customers have commented that our issue titles are confusing. Some titles can be interpreted multiple ways, and an issue’s impact isn’t always clear from the title alone. In response, we’ve restructured issue titles to be more readable.

Titles will no longer list error occurrences by percentage. Instead, if a reproduction step triggers the error more than 50% of the time, the title will indicate the error often occurs at the step listed. If the reproduction step triggers the error 100% of the time, the title will indicate the error always occurs at the step listed.

Examples:

JS Error: Cannot read properties of null (reading ‘style’)
Occurs in bundle.js

JS Error: Smile UI is not defined
Occurs in bundle.js, often when users load page

HTTP Error: 400
Occurs in 400-bigcommerce.route.com/add, always when user clicked Checkout

This update won’t affect issue ID numbers, nor will it affect how Noibu collects and presents issue data. For a detailed breakdown of the error’s occurrence, see the Last Reproduction Steps section on the Developer tab.

Closed-Fixed Issue Filtering

We’ve started tracking the date and time an issue’s status is updated to Closed-Fixed, and added this data point to the All Issues table. With this update, you can filter the table to pull issues marked Closed-Fixed within a given timeframe.

You can also check when an issue was marked Closed-Fixed by hovering over the check icon in the State column; this information is also listed or by opening the issue’s Overview tab.