search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.57k stars 4.13k forks source link

Design: On replay details, link back to the page where users started their debugging journey #41847

Closed ryan953 closed 1 year ago

ryan953 commented 1 year ago

Feedback was:

switching tabs (dom/network/etc) should probably use history.replace so I don’t have to hit back 5 times to get back to the issue I was on related to the above, I wish that we retained some context of the sentry issue I was just on (like a breadcrumb or something, or lettings them play from the issue details page) so I don’t have to hunt for the error to get back to where I was from malachi

The tabs thing could go either way imo, and we've got it updating the history stack for a reason. But that might not be such a big deal for folks if we have a persistent link back to where they came from.

Something like this in the header would solve the problem:

Image

ryan953 commented 1 year ago

cc @Jesse-Box

ryan953 commented 1 year ago

other feedback from ben:

I disagree with this ticket — we dont do this anywhere else You’re just recreating browser history Eg performance doesnt give you a paper trail of every page you visited I’d sooner have a ticket re malachi’s “what level of tab creates browser history and what doesnt” and thats a product-wide convo for coreui to drive imo Malachi

ryan953 commented 1 year ago

@malwilley is going to see about getting guidance on when to use browser history and when not. Closing this.