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

### 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)*