Environment

SaaS (https://sentry.io/)

Steps to Reproduce

trigger an error from "development" env and another one from "producion" env

Expected Result

issues are not grouped, and most importantly, Slack notifications are separated.

Actual Result

Issues are grouped, and the first environment in which the error occurs handles the Slack notification.

In our case, we noticed than errors coming from scheduled jobs trigger at the same time on development and production environment. The development instance gets it just a bit before the production env. So the issue is created and notified to the development-errors slack channel. The same error on production env being grouped with it, it is not considered as a new error, and the prod-errors Slack notification isn't triggered.
This is very annoying, as some production errors end up being hidden because of their development equivalent.

Issues from different environment should never be grouped together (at least it should be an option to do so).

Product Area

Alerts

Link

No response

DSN

https://[email protected]/6458945

Version

No response