search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.25k stars 4.21k forks source link

Slack context in Sentry issue #71898

Open namoscato opened 5 months ago

namoscato commented 5 months ago

Problem Statement

We leverage the Slack integration to notify us about new / regressed issues (and the recent Slack integration updates have been great, specifically the UX change around threading re-opened issues). We often find ourselves dropping a comment on Sentry issues with a link to relevant Slack threads that contain historic triage context. This facilitates future triaging should the issue regress, but given the manual process, people often forget to create this bi-directional relationship.

Solution Brainstorm

It would be great to expose Slack message / thread links somewhere in the Sentry issue page itself.

Alternatively, the comments themselves could sync bi-directionally as described in https://github.com/getsentry/sentry/issues/71175.

Product Area

Issues

getsantry[bot] commented 5 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 5 months ago

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

Dhrumil-Sentry commented 5 months ago

Thanks for this feedback! , We'll add it to our backlog but we don't anticipate working on this anytime soon