Streamline your items workflow

September 22nd, 2020 • By Gabriella Papp

Overview

Chances are you have multiple incoming occurrences in your Rollbar projects, grouped into items, appearing in your Item list, one after another. You also start to receive notifications pouring in your inbox. Now, you might as well keep your incoming items organized and clean by Rollbar’s useful options of:

  • Setting up statuses for your items, that determine how they appear and behave,
  • Triaging and rating them based on their severity level.

This way you can make sure your item list is transparent, you will not be spammed by irrelevant notifications, provide clear visibility for your teams who manage the same project by appropriately triaging your errors and setting up the relevant severity level and status, to speed up the process of debugging, making sure everyone focuses their attention on the relevant things!

Item statuses

At Rollbar, we offer the chance to assign 3 statuses for your items: Active, Resolved, Muted.

Active items

All items start as active. Active means that the error is present and on-going and it requires your attention. It could represent a bug that has not yet been fixed or an intermittent ongoing backend issue.

Active items:

  • Appear on the Dashboard
  • Trigger notifications on their first occurrence and when thresholds are crossed (according to your notification rules)
  • Count for billing purposes
  • Can be changed to Resolved and Muted

Resolved items

When you believe your item is fixed or if you want to be notified if the bug re-appears you can mark it as Resolved. If possible you should include the version in which the item is fixed for future reference, as it will prevent it from being reactivated fore you deploy the new code version. This way you can also prevent your items from being reactivated by clients that are still running the old code.

Resolved items:

  • Won’t appear on the dashboard (but you can still filter for them)
  • Will be reactivated when the error occurs again in a newer code version, triggering a notification
  • Count for billing purposes
  • Can be Reactivated or set to Muted

Error I crashed more

Muted items

If you consider an item as a non-issue for the time or currently don’t want to work on it, you can set it to Muted. Errors that currently aren’t worth investigating can be set to Muted, making sure they stay out of sight. Muted items are still searchable and can be indexed.

Muted items:

  • Won’t appear on the dashboard (but you can filter for them)
  • Remain muted even if they occur again
  • Count for billing purposes
  • Can be set to Resolved or Active

Error - I crashed

Update your item statuses

There are many ways to update item statuses, you can:

  • Set the item status to Active, Resolved or Muted manually in the UI on the Item list view or the Item details view
  • Set it to Active, Resolved or Muted via Rollbar API
  • Automatically resolve via commit message
  • Automatically resolve on deploy
  • Automatically resolve when an item hasn’t occurred in a set amount of days
  • Resolve when a Jira issue is closed

Severity levels

All Rollbar Items have severity levels. Properly setting up your severity level can reduce the noise in your Items/Dashboard/Versions view and your notifications and also reduce alert fatigue. There are 5 levels:

  • Critical
  • Error
  • Warning
  • Info
  • Debug

The default severity level for all unhandled items is Error, which you can change based on your system of prioritization. You can easily change the severity levels in the UI manually. Severity levels can be used as criteria for notification rules. It is useful if you only want to receive notifications about a certain level of bugs. It can also be used as a filter in RQL or the Item/Dashboard/Versions view, so you can manage the visibility of your items.

Items Workflow

Learn more

Check out our Docs to get more details on how to change your item statuses!

Get the latest updates delivered to your inbox.