Skip to content

Duplicated emails for escalating issues #124455

Description

@filips123

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Have an error monitor for issues.
  2. Configure alert for sending email alerts when a new issue is created, when a resolved issue regresses, and when an issue escalates.
  3. Wait until some issue escalates.

Expected Result

There should be only one alert email. Even if both project-specific alert rule is configured and the user has "Workflow Notifications" enabled, Sentry should notice that and send only the alert rule email. The email subject should contain both the issue ID and the issue title. Potentially, although this is more like a feature reqest, it should also contain the issue status.

This is the case when the issue is created or has regressed. Also, in those two cases, the email from the alert rule clearly says "Regressed issue" or "New issue":

Regressed issue alert New issue alert

Actual Result

The two emails are sent.

The first one has a subject only "Re: ISSUE-ID" and contains "Issue marked as escalating" title.

First email

Another problem with this email is that compared to alert rule emails, this email doesn't specify the issue title in the email subject.

The second email, which often arrives a few minutes later, but sometimes almost at the same time, has a subject "ISSUE-ID - Issue name/description", and contains "New Alert" title.

Second email

A problem with this email is also that it only says "New Alert" and not "Escalated issue", unlike the other two alert email types.

I assume the first email is sent because I have "Workflow Notifications" enabled for subscribed issues in account/personal notifications, and the second one is sent because of the monitor/alert rule.

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions