Jira-Sentry link post merge leaves broken URL in Jira link comments

[kalbasa28]

Problem Statement

If a Sentry issue is linked to a Jira bug and then merged, there is a chance (maybe even 100%) that the issue shortid will change, the Jira issue will get unlinked (as a result of merging into another issue) and the link posted on the bug will become inactive.

Solution Brainstorm

Would it be feasible to make the links redirect to the main (merged) bucket and/or maybe relink the issues post merge? Or simply always merge into the issue that already has connections (Jira link in this case) as opposed to the one with the most events?

Product Area

Issues

We want to define a set of lightweight metrics that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that do NOT overlap with Tracing. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

• Node.js runtime metrics (e.g., event loop delay, heap usage)
• Prisma-related metrics in Next.js
• Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

Candidate Metrics (add more below)

• …

(please also add ideas, questions or examples in comments)

[linear]

ENG-5545 Jira-Sentry link post merge leaves broken URL in Jira link comments

[getsantry]

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

[aldy505]

Hi @kalbasa28, are you seeing this on SaaS (https://sentry.io / their cloud version) or are you using self-hosted Sentry?

[sentaur-athena]

@kalbasa28 issue short IDs are not changed when resolved. I'm not sure what you mean by after merge they change. Can you explain the problem with more details?

[kalbasa28]

@aldy505 this is on cloud Sentry

@sentaur-athena Yes, sorry, perhaps this was not very clear - resolving the issue is not the concern here. I will give a scenario where this is annoying to deal with.

1. ISSUE-1 gets linked to Jira bug
2. URL of ISSUE-1 is posted automatically in the Jira bug comments ("Linked Sentry Issue: ISSUE-1")
3. ISSUE-1 is merged into ISSUE-2
4. URL of ISSUE-1 becomes inactive (still remains in the Jira bug comments)
5. Since the hyperlink text is the shortid (in this case, shortid is ISSUE-1), it becomes misleading since you are no longer able to look it up (effectively the shortid changes to ISSUE-2)

So the problem is that Jira bug comments get polluted with bad URL's if issues are merged and the link to Jira is lost on the original Sentry issue.

Additionally, a workaround of always manually merging into the bucket containing the Jira link was suggested, but this is not very reliable since such manual merging is only possible through the Similar Issues tab as far as I know.

Hope this clears it up a little, let me know if there's anything else that I might've missed or if you have any thoughts.