Open JimJafar opened 10 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-user-feedback for triage ⏲️
Thanks for raising this. Makes sense.
On the widget, we have an option called showEmail
. Would make sense to add the same
https://docs.sentry.io/platforms/javascript/user-feedback/configuration/
@bruno-garcia actually for GDPR and since you probably have a userId in the log, I think it makes sense to have the name field be optional too. Less noise in the form and less barrier to the user entering something. I know we can pre-fill the fields, but still - a single textarea is less off-putting to a user who has just encountered a blocking bug.
I've updated the issue title and description, hope that's OK.
Thanks for looking into this!
you probably have a userId in the log,
There's no userId by default, so you'd need to add it explicitly and before doing so, get consent from the user if that's needed.
I think it makes sense to have the name field be optional too. I know we can pre-fill the fields, but still - a single textarea is less off-putting to a user who has just encountered a blocking bug.
I agree!
I've updated the issue title and description, hope that's OK.
Thank you!
Problem Statement
We don't want to store our user's name & email addresses in Sentry (less PII for GDPR compliance), but the email field in the crash report dialog is required.
Solution Brainstorm
Add
showNameField
andshowEmailField
properties toReportDialogOptions
that aretrue
by default. If set tofalse
, the fields would be omitted from the form. You could still allowuser.name
anduser.email
to be provided for those consumers who wish to record them but don't want to trouble their users with entering it.Product Area
User Feedback