Skip to main content

Custom Environment Folder

Environments filter incidents on properties such as source and priority and group them together for easy visibility and action.

Each environment breaks incidents out into folders based on associated status. All environments include default folders for Active, Unhandled, Shared, Snoozed, Maintenance, and Resolved.

You can now create up to three custom incident folders per environment.

Custom folders appear above the standard folders in the expanded environment view.

Limited availability

This feature has limited availability. If you are interested in enabling this functionality for your organization, contact your BigPanda account team.

Folder Logic

Custom folders can be defined by either incident status or a specific incident tag value.

Incident status

Combine incidents from multiple status folders into a single custom folder. You can select any combination of statuses (active, resolved, unhandled, shared, snoozed, maintenance) — not just active and resolved.

For example, you could create a folder that shows both Active and Resolved incidents together, useful for teams whose workflow requires visibility into both states at once.

The 24-hour resolve window still applies to resolved incidents in custom folders.

Incident tag

Filter incidents by a specific incident tag value. Available operators include equals, doesn't equal, and empty.

For example, you could create a folder that shows all incidents where a specific tag is empty, ensuring operators can quickly identify incidents that still need attention.

When an incident tag filter is applied, incidents must pass both the environment filter and the custom folder filter to appear.

API routes

Custom folders can be queried through the Incidents API.

To retrieve incidents from a custom folder, use:

GET /resources/v2.0/environments/<environment_id>/feed/incidents

With query parameters:

sort_by=last_change
page_size=50
page=1
custom_folders=true
folder=<value>

folder=<value> should be either a combination of statuses using url-encoding (for example: active%2Cunhandled) or a custom folder name (for example: test%20space)