getsentry
[User Feedback] Context shown in the replay is still not enough to understand the feedback message
Problem Statement
In the cases where a user takes 30s or longer to type a feedback message, context for what was happening leading up to the feedback message inside the replay is often lost/missing.
Previous ticket on this: https://github.com/getsentry/sentry/issues/68100 Customer report: https://discord.com/channels/621778831602221064/1239508677430349854/1239508677430349854
This was also raised internally by @ceorourke while trying to debug a feedback. The idea of having the buffer keep track of 'bytes' might really help here. @billyvg thoughts?
Hmm I thought we had changed it so we flushed when the feedback modal was opened?
We do need to generally improve our buffering so that we can support buffering more events when possible.
I haven't looked closely at it lately, so I can't say if we still experience the same issue, but this is the main reason why my team a few months ago went from being incredibly impressed with the User Feedback + Replay integration, to instead start considering the replays to be mostly waste.
In other words, a solution would be a huge improvement for us.
Love the replay system, but want to add to the others that it loses alot of value when manually reported bugs only have me looking at the user writing the bug itself.
