getsentry
Customer sees fewer User Feedback reports on the new page than on the old page, given the same filter criteria
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Use a project that has good dataset of genuine user feedbacks, open the new and old UI and use the exact same filter criteria, you will see that the number of results don't match.
Expected Result
Customer expects to see the same reports in either new or old UI.
Actual Result
Use a project that has good dataset of genuine user feedbacks, open the new and old UI and use the exact same filter criteria, you will see that the number of results don't match.
Product Area
User Feedback
Link
No response
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito
![getsantry[bot] avatar](https://avatars.githubusercontent.com/in/66573?v=4 "Published by a pub.dev verified publisher"){kind=small}
@bruno-garcia I have also observed this happening. in my case, we use two ways of submitting user feedback (both through the user feedback api endpoint):
- If a crash occurs, we allow someone to submit user feedback and associate it with the event ID of the crash (generated with
sentry.CaptureException). This seems to show up in both the new and old user feedback UIs. - The user can also submit feedback at any time. In this case, we call
sentry.CaptureMessage(via the Go SDK), and associate the user feedback with the newly generated message. This shows up in the old user feedback UI but not the new one.
~Is it possible that the new UI is filtering out user feedback associated with sentry "messages" rather than sentry "errors"? Is this intended behavior?~ Edit: I was wrong about this being the problem; I will update here if I'm able to repro the conditions that lead to a user feedback event being shown only in the old view, but let me know if there are any debugging steps I could take to provide more info.
N.B. we haven't been using this feature very long, so we have a limited set of events; I could be wrong about what the cause is for this but I can generate some more events to test this out.
Closing this since last update was in May and seems resolved. Feel free to open a new issue if you're experiencing any problems