Skip to content

A regressed issue should edit the Slack message to mark it as such #58433

@armenzg

Description

@armenzg

You can see this issue resolved by me via Slack:
image

After I resolved it, another event came in and regressed it:
image

It shows as resolved in Slack. We should edit the Slack message and mark it as re-opened.

Ideally, we should do a 2-way sync between Sentry and every integration. We can punt that to later.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions