> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/production/regression-alerts.md).

# Regression Alerts

BugSplat can be configured to notify developers when a defect marked as Closed recurs in a newer version of their software. Crash groups can have one of four statuses: Open, Closed, Regression, and Ignored. A regression happens when a crash group is marked as closed, but an instance of the crash occurs in a newer version.

In BugSplat, developers can update the status of a group by clicking the Open, Closed, Regression, or Ignored badge and selecting a new status.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fp1E8FaYtwjmju12rbAL9%2Fstatus-open-closed.gif?alt=media&amp;token=83913e51-9f5d-4826-8c19-b880d6444c1c" alt=""><figcaption><p>Set the Status of a Group to Closed</p></figcaption></figure>

When a group's status is set to Closed, BugSplat notes the latest version of the application. If the same crash arrives at BugSplat from a newer version, BugSplat considers this a regression and sets the status from Closed to Regression accordingly.

### Alerts

BugSplat can be configured to send a [notification](/guides/integrating-with-tools.md) via [Discord](/guides/integrating-with-tools/messanger-apps/discord.md), [Teams](/guides/integrating-with-tools/messanger-apps/microsoft-teams.md), or [Slack](/guides/integrating-with-tools/messanger-apps/slack.md) when a regression occurs. Follow the links in the notifications documentation and choose the Regression Alerts option once you've connected to your favorite messaging platform.

### Defect Tracker Sync

If you're using [Jira](/guides/integrating-with-tools/issue-trackers/jira.md), BugSplat can be configured to update the status of linked issues. On the [Defect Trackers](https://app.bugsplat.com/v2/database/integrations?database=Fred#defect-trackers) page set the status you'd like BugSplat to set on Jira when a crash is identified as a regression.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2FRfqLm0TaqVAAeNDT9g6m%2Fregression-status.gif?alt=media&amp;token=eccffd10-8bbd-495a-9fda-1f0417c79dfa" alt=""><figcaption><p>Mapping the Jira Regression Status</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/guides/production/regression-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.