sentry icon indicating copy to clipboard operation
sentry copied to clipboard

Github 2 Way Sync

Open prashantchothani opened this issue 1 year ago • 6 comments
trafficstars

Problem Statement

There is no 2 way sync with Issues created on Sentry to Github

Solution Brainstorm

We need to have 2 Way Sync with Github for Issues just like you have for Jira. This is very important to track error resolution metrics and also tracking reopening of bugs.

Product Area

Alerts

prashantchothani avatar Feb 29 '24 13:02 prashantchothani

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] avatar Feb 29 '24 13:02 getsantry[bot]

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

getsantry[bot] avatar Feb 29 '24 16:02 getsantry[bot]

This is a valid request, Adding this to our backlog. We will update this issue as we have more details

Dhrumil-Sentry avatar Feb 29 '24 16:02 Dhrumil-Sentry

@Dhrumil-Sentry Whenever this is picked up, can we also have in the Link Settings to set the project name as well as minimum apart from labels ?

prashantchothani avatar May 02 '24 06:05 prashantchothani

@prashantchothani could you please clarify that request? Do you mean you want the project name to be added as a default to the ticket body?

Dhrumil-Sentry avatar May 03 '24 21:05 Dhrumil-Sentry

@Dhrumil-Sentry In the Issue that is created in Github, we would like to have project name to be added which we can specify in the Link Settings.

Another thing we noticed that in the 2 way sync, the Issue which was created once by Sentry in Github and then if that was fixed and closed, then the status is not being set to reopened when the same bug occurs again. This is a bug

prashantchothani avatar May 21 '24 10:05 prashantchothani

Another request for issue status sync in GitHub: https://sentry.zendesk.com/agent/tickets/146638

When a linked issue is closed in GH, the issue in Sentry should be marked as resolved (and vice-versa). The same for when an issue is reopened in GitHub or regressed in Sentry.

rodolfoBee avatar Mar 13 '25 14:03 rodolfoBee

We're prioritizing this for Q2. @GabeVillalobos please make sure this is included in feature parity doc for ticketing integrations.

sentaur-athena avatar Mar 14 '25 22:03 sentaur-athena