Issue details remain useful only when project access is enforced at the request boundary.
Developers need fast production context, while project owners need removed access to mean removed access.
Who you’d be doing this for
“I removed a contractor from the payments project, then found they could still open an old issue link.”
Ana Ribeiro · Application Developer
Uses project-scoped access to investigate errors for several services within one engineering organization.
What is at stake
A removed project member can still open issue details through an old link. You have to protect project boundaries without slowing authorized production investigation.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- project isolation vs. incident investigation speed
- fast containment vs. durable authorization control
- reporter confidence vs. incomplete validation
Why Sentry
Issue details hold the error context developers use to diagnose production failures across customer projects.
Written with these in mind
Not your kind of problem? 20 more at Sentry, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.