Link issue to multiple JIRA issues

[ttzviiol]

Problem Statement

We would like to have an option to link multiple JIRA issues to a single Sentry issue.
This is needed since sometimes an issue is resolved by a JIRA issue, but later on it's happened again but from a different workflow, or different reason.

Solution Brainstorm

No response

Product Area

Issues

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[sentaur-athena]

Thanks for providing feedback. I take this to our product team to see how we can address this better and get back to you.

[sentaur-athena]

After discussions with the team, we think it's better experience to keep issues 1 to 1. Having multiple issues for one issue brings the question of which one to sync with and how to take care of sync conflicts. Ideally issue grouping should create a new sentry issue and then Jira issue if the root cause is very different and improving issue grouping is always part of our ongoing work.

[ttzviiol]

So what should we do in the following scenario:
We have a Sentry issue that have multiple different messages, but they are 1 issue because it's the same stack trace.
Both needs to be addressed in different JIRA issues on our side.
How should we connect them both?
Or how do we ungroup a Sentry issue that was auto merged by Sentry because they share the same stack trace?

[sentaur-athena]

Highly depends on your processes but I would keep on jira ticket, the one that is in sync with Sentry as a master ticket and create sub tickets for different events that need to be assigned to different people.