You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I browse through the Issues list and find one that catches my eye, what I want to do is navigate to the source files listed in the stack trace. At the moment, I must expand the Issue in the list, copy the stack trace, run Code → Analyze Stack Trace or Thread Dump, then massage the stack trace into a usable format (mostly by prepending source roots to create absolute paths for valid files).
Describe the solution you'd like
It would be amazing if path mappings could be configured for each Sentry project, so paths originating from deployed servers could be mapped to local files. Then, ideally, an expanded Issue in the list would link these paths, allowing navigation in a single click. Additionally (or alternatively), it would be great to have a button to open a new Analyze Stack Trace tool window with the massaged stack trace inside.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When I browse through the Issues list and find one that catches my eye, what I want to do is navigate to the source files listed in the stack trace. At the moment, I must expand the Issue in the list, copy the stack trace, run Code → Analyze Stack Trace or Thread Dump, then massage the stack trace into a usable format (mostly by prepending source roots to create absolute paths for valid files).
Describe the solution you'd like
It would be amazing if path mappings could be configured for each Sentry project, so paths originating from deployed servers could be mapped to local files. Then, ideally, an expanded Issue in the list would link these paths, allowing navigation in a single click. Additionally (or alternatively), it would be great to have a button to open a new Analyze Stack Trace tool window with the massaged stack trace inside.
Additional context
No response
The text was updated successfully, but these errors were encountered: