getsentry / getsentry/sentry

Un-bundle permissions to unlink Jira issue and deleting events.

Open
#66,227 9 comments 3 reactions 0 assignees View on GitHub
Feature Metrics Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

Currently, all normal users have permission to add a Jira issue to a Sentry issue but not remove it. What if they made a mistake?

To give them the power to unlink a Jira issue, I have to give them the power to potentially delete every error in our project.

Or, more likely, accidentally delete an issue. These do not seem like appropriate permissions to group together.

### Solution Brainstorm

Add a new permission to create/edit/delete linked issues. At least for our use case, it can be one permission for all rather than more fine grained.

### Product Area

Settings - Members

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.