When your application surfaces bugs, it might put your Support team in a difficult position in understanding the impact of an error on users and customers and who might be the right team to assign the issue to. A proactive approach is essential: when users are affected by bugs in your software, it corrupts the customer experience, leading to users eventually choosing to stop using your product.
In this article, we will walk you through how you can help Support team enablement with certain features of Rollbar:
- People tracking provides visibility over which users of the application are impacted by an error
- Item Severity level and error frequency help prioritize errors
- Automated Issue Tracking helps you to assign a developer to an issue to ensure resolution
Rollbar helps your team understand the impact of errors on specific users, and you will be able to prioritize and assign errors based on the frequency of bugs and the volume/value of customers impacted by them. This will enable your team to address and resolve customer issues faster and with more context.
When an error occurs in your application, one of the first questions is “How many people are affected?” When you have People tracking set up, you will have visibility on how the errors in your application have impacted your customers. You can check the People menu in the Item details view to see:
- Which customers were affected by any one error:
This gives you details on a particular user, how many errors have affected that person, and the last time it occurred. If you click on a selected user’s name, you will get extra visibility on:
- The history of errors experienced by a particular person:
You will see the affected environment, the date, and time of the last occurrence and additional details:
- the specific item that is linked to the error,
- the Severity level and the status of the item
Checking the item gives you context on the error that will help you assign the error to the right person.
On the People Menu in the navigation, you will get the list of all people who have ever experienced an error, sorted by most recent error. Currently, we do not support people data across multiple projects. You can select a single project to view People data. In the Affected People view, you will be able to further filter for:
- specific users by e-mail address or username
This can help Support teams identify the error that has affected a particular user, and understand the impact of a customer-reported issue by matching it with the associated Rollbar item. The contextual data enables faster resolution of issues.
Clicking “Explore as RQL query” from the Person details will return all items that have affected the given person:
And clicking “Explore as RQL query” from the People tab in the Item detail menu will return all people affected by the given item:
All Rollbar items have a severity level:
- Error (default severity level for unhandled exceptions)
You can set the severity levels in the UI in the Item list or Item details. Severity levels can be used as filters in notification rules, in the dashboard, and in RQL. Properly configured severity levels can reduce noise and alert fatigue and speed up the process of triaging and prioritizing errors.
You can read more about Severity levels and Item statuses.
The Items list view gives additional insights to further help prioritize errors:
- a 24-hour trend, with the option to drill down to see the number of occurrences for a particular timeframe in the last 24 hours, and
- the total number of incoming occurrences per items,
- a counter showing the time since the error last occurred.
With the help of this high-level view, your Support team can get information on how frequently errors are occurring. In combination with People tracking, they will be able to triage and prioritize errors and assign them to the developers.
Once errors are discovered and prioritized, it is essential to assign them to the right developer in a timely manner for fixing. You can save time and debug faster by integrating an issue tracking tool with your Rollbar projects.
Manual error assignment can be time-consuming and error-prone. Automatically assign an error to a developer to ensure resolution. Set up rules to avoid the need for manual intervention. Rules can be filtered to only trigger in specific conditions (e.g., only create issues for items in production that have level error or higher).
Rollbar can integrate with many popular issue tracking softwares, making it easy to track Rollbar detected errors in your already existing workflow.
Read our article on Jira integration best practices for some tips and tricks.
Updated about 2 months ago