Subscribe to new issues in a release

[ryanwilsonperkin]

Summary

A user can subscribe to notifications of new issues that appear in a specific release.

Motivation

We have (and I think this is a pretty common scenario) a project in Sentry with a large volume of errors in it. When we put out a new deployment, we often find ourselves watching the "New Issues" tab on the associated Sentry Release and refreshing for a little while. It would be great if we could instead tell the Release to notify us if there's a new issue that appears.

Additional Context

I imagine a potential user experience for this could be a button on the release page that can be clicked to subscribe to, looking like this:

It would also be useful to be able to subscribe a user programmatically with the sentry CLI, since we could then automatically subscribe people when they issue a deploy.

[adhiraj]

@ryanwilsonperkin we generally consider "new issue" to be an alert, not a workflow notification. Assuming that's what you want, do you watch for issues on every release, or only the occasional important ones? If the former, how would you expect this to behave differently from the "every new issue" alert rule we already have? If the latter, would you like to be unsubscribed from it after a while (to not keep receiving alerts from releases far in the past)?

[ryanwilsonperkin]

Hi @adhiraj, thanks for your response.

Assuming that's what you want, do you watch for issues on every release, or only the occasional important ones?

I'm thinking specifically about the occasional important ones. We have a large number of developers contributing to a shared project, and they don't necessarily want to be alerted to every new issue for that Sentry project. They do however really want to be aware of any new issues that occur in a release that they published.

would you like to be unsubscribed from it after a while (to not keep receiving alerts from releases far in the past)

That's an interesting angle that I hadn't considered. I'd be perfectly happy to manually unsubscribe from the release in this scenario, but maybe as a stretch goal of the feature we could consider a feature that allowed me to say "Subscribe to this release for the next hour|day|week|etc". I imagine the UI could look something like the dropdown on "Resolve after
this|next|specific release".

Happy to answer other questions you might have, I'd love to help see this feature through if it's something your team is interested in working on.

[adhiraj]

Is this equivalent to creating an alert rule for new issues in release XYZ?

(Not suggesting that that's the optimal UX, just wondering if that's effectively what you're looking for. Also one limitation is that we don't currently have the ability to send alerts to specific users or teams)

[ryanwilsonperkin]

@adhiraj yes I think that would be functionally equivalent with the one exception that we would want it to be a notification for a specific user or team. Without the send the notification specifically, it falls into the same shortcomings as a more general rule for "notify on all new issues".

[BYK]

Closing this issue due to staleness. Feel free to comment here if you think we should still work on this.

[adhiraj]

a) do we need a personal subscription (i.e. any user who subscribes gets notifications), or to be able to specify a user or team that new issues in the release should go to? b) do we need to be able to send this to integrations (e.g. slack)?

[ryanwilsonperkin]

a) do we need a personal subscription (i.e. any user who subscribes gets notifications), or to be able to specify a user or team that new issues in the release should go to?

Both would likely be desirable. We'd want the ability to opt people in as part of our CD pipeline, but others might also choose to opt in when visiting the release page.

b) do we need to be able to send this to integrations (e.g. slack)?

Doesn't personally matter to me, since we'd handle that separately either way.

I should note that I no longer work for the employer who I initially opened this on behalf of, and my new role doesn't have me using sentry. That said, I'd still advocate for this feature because it seems useful (and I want to use sentry again in the future 😉)