2-way sync with Pivotal Tracker

### Problem Statement

With today's Pivotal Tracker integration, data is no longer synced between Pivotal Tracker and Sentry after creating a Pivotal Tracker bug from a Sentry Issue.

For example:

* resolving a bug in Pivotal Tracker, doesn't mark the issue as resolved in Sentry
* assigning a person in Pivotal Tracker doesn't assign a person in Sentry

This means issues need to be managed from 2 locations, not just 1.

### Solution Brainstorm

Our desired workflow is to use Sentry for issue report collection and triage. Once it's determined to be a bug we'll fix, our workflow moves to Pivotal Tracker.

It would be great if changes we make in Pivotal Tracker could be reflected in Sentry to avoid having to mark issues as resolved twice, ie once in Pivotal Tracker and once in Sentry.

Likewise, if we were to make changes in Sentry, such as marking an issue resolved or assigning it to someone, those changes should also be able to propagate to a linked work item in Pivotal Tracker.

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