User Feedback Beta Launch: We Want to Hear Your Feedback #60134
Replies: 19 comments 49 replies
-
|
Is there a webhook, or way to create a Slack integration for inbound feedback? I couldn't see in docs. One of the most valuable aspects of feedback buttons like this is surfacing said feedback to developers and designers, revealing loads of quick-win suggestions to improve a product. If it's only visible in Sentry's web app it'll be largely forgotten. Border radius could be a configurable property too. It's hardcoded 20px atm. |
Beta Was this translation helpful? Give feedback.
-
|
You can create alerts: https://docs.sentry.io/product/user-feedback/#getting-user-feedback-alerts |
Beta Was this translation helpful? Give feedback.
-
|
^ Yup, and get the feedback submissions straight to your Slack channels! |
Beta Was this translation helpful? Give feedback.
-
|
Ah, perfect 👌🏼 |
Beta Was this translation helpful? Give feedback.
-
|
The current version of the JavaScript SDK I'm using is 7.86.0. After configuring the feedback feature, I encountered an error message saying, "You are using new Feedback() even though this bundle does not include Feedback." |
Beta Was this translation helpful? Give feedback.
-
|
@yxplus1116 can you create a ticket on https://github.com/getsentry/sentry-javascript/issues/new/choose? Please include your |
Beta Was this translation helpful? Give feedback.
-
|
Have you resolved this issue? |
Beta Was this translation helpful? Give feedback.
-
|
@amaimasque We never received the issue with details. Could you please create a ticket explaining your set up? SDK version, your |
Beta Was this translation helpful? Give feedback.
-
|
Environment:
Description: Steps to Reproduce:
Observations:
Questions:
Any suggestions or insights into this issue would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
Calling |
Beta Was this translation helpful? Give feedback.
-
|
Hello Billyvg, Thank you for your prompt response. Since my last message, I have upgraded to the latest SDK version. However, I am still encountering issues with feedback not appearing in Sentry. I am using the following code snippet to send feedback: sendFeedback({
message: data.message,
email: data.email,
name: data.name,
}, {
includeReplay: true,
});The POST request header appears to be correct: The request payload also seems to be in order, with no apparent errors. Despite this, my Sentry User Feedback inbox is empty. |
Beta Was this translation helpful? Give feedback.
-
|
@walter-greefkes Can you email me your org slug? billy at sentry.io |
Beta Was this translation helpful? Give feedback.
-
|
Is a
In https://docs.sentry.io/platforms/javascript/user-feedback/configuration/#crash-report-modal
|
Beta Was this translation helpful? Give feedback.
-
|
We have not talked about localization yet, can you copy this into a new ticket here, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
getsentry/sentry-javascript#10209 added as a Feature Request – hope that's the right issue type... |
Beta Was this translation helpful? Give feedback.
-
|
Suggestion Add ability to export feedback as CSV/other formats. |
Beta Was this translation helpful? Give feedback.
-
|
how to ignore some errors? (always set it in 'dropped' and skip quote use) |
Beta Was this translation helpful? Give feedback.
-
|
You can filter events client side through If you can't filter it client-side for some reason, take a look at inbound filters: https://docs.sentry.io/product/data-management-settings/filtering/ |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to exclude the feedback on certain URLs without us having to manually do it? i.e. right now it shows up on logged out pages too, and I'd love to have a list of URLs it doesnt show up on. For context we are using nextjs. This could also be something we missed reading in the config. |
Beta Was this translation helpful? Give feedback.
-
|
There isn't a configuration option for this, you will have to manually do it. At sentry we have a component + hook for the widget and place it on the views where we want it: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Something like this is what we went with, however, I think this is a common enough case where having an option for it would be helpful :) |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to add custom data to a feedback form submission? I don't see one. We would like to add some context to the submissions to better handle the feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Our users will be on a specific page, which we can get from the sent URL, but there are other "ephemeral state" things that might be causing them to submit said feedback (in our case a Svelte store, but could be a snapshot or selector data from Redux, etc.) A simple tag would probably not be sufficient. |
Beta Was this translation helpful? Give feedback.
-
|
@orbiteleven Are you using our Session Replay product? Those are tied to feedback submissions and we offer a Redux plugin for breadcrumbs: https://docs.sentry.io/platforms/javascript/guides/react/features/redux/ |
Beta Was this translation helpful? Give feedback.
-
|
Hey @jas-kas. Sorry for the radio silence. We're not actually using React/Redux but rather Svelte/SvelteKit, so this won't work for us. I would imagine it could be something like event context, but it does not seem like |
Beta Was this translation helpful? Give feedback.
-
|
We have a GitHub ticket to track that request: getsentry/sentry-javascript#10916 Our custom breadcrumbs can help fulfill this today as well: https://docs.sentry.io/platforms/javascript/enriching-events/breadcrumbs/#customize-breadcrumbs |
Beta Was this translation helpful? Give feedback.
-
|
@orbiteleven we now allow for custom context, see getsentry/sentry-javascript#10916 (comment) :) |
Beta Was this translation helpful? Give feedback.
-
|
Is there some way that a user can see their submissions to check for status, responses, etc.? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for getting back to me!
So you're often receiving multiple feedbacks from the same user? Hence, why you'd like a report where we can show 'all submitted issues' for a particular person?
So if I understand correctly you have a way for users to see the status of their submission via Linear? For the gap where the user "submitted but don't get anything back", we're likely not going to do any automatic comms to the end-user as soon as we receive a new feedback. This is because not all feedbacks end up being actioned, so we don't want to set that expectation with the user. However, we're looking at having an option in the UI to trigger an email to the end-user when a Sentry user has decided to action on a feedback. Would that be helpful for your workflow? |
Beta Was this translation helpful? Give feedback.
-
|
hey @jas-kas Short answer: yes, having some sort of "notify end user of action" would help. I totally understand that you don't want to over-implement here, so perhaps there's some way for us to handle the end-user confirmation? I guess we could do something with |
Beta Was this translation helpful? Give feedback.
-
|
Right, Sentry's main differentiator for our User Feedback Widget is providing debugging context (errors, replays, tags, etc) as it relates to a feedback submission, reducing the back and forth required with the end-user -- this is something Zendesk/Hubspot cannot provide out-of-the-box. However, if you'd like sophistication customer communication workflows, it might make sense to auto-create a Zendesk/Hubspot ticket for every Sentry feedback submission. Or, alternatively, connect Sentry data to users who submit tickets via Zendesk/Hubspot in other ways (for example, search by user email and time range on our Replay page to find a relevant replay video). I will check with the team on the custom data case that you described above and see if there are other options there. :) |
Beta Was this translation helpful? Give feedback.
-
|
@orbiteleven FYI this may be helpful - https://docs.sentry.io/platforms/javascript/session-replay/understanding-sessions/#connect-replays-with-support-software |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again, @jas-kas. If we do end up rolling our own Zendesk/Sentry/whatever hybrid, something like that could be useful. |
Beta Was this translation helpful? Give feedback.
-
|
H @jas-kas Thank you for this nice feature, I was waiting it for a long time. I would know if you have a plan for creating another components for another type of feedback ( Like / Dislike ). Example
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @jas-kas , Thank you for these new improvements, I would suggest a classification for the feedback ( reaction, feature request, issue ) like Microsoft:
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @alamenai 👋 Thanks for writing in and for sharing this feature request. We don't have a way to surface classifications via the out-of-the-box web widget at the moment, but you can always use your own widget to meet this need. https://docs.sentry.io/platforms/javascript/user-feedback/configuration/#bring-your-own-widget and set a custom tag so you can reflect what classification selection was made inside the User Feedback Details UI |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @jas-kas <3 , Yes it seems functional for the time being and the customization is easy with the API. |
Beta Was this translation helpful? Give feedback.
-
|
I've been using User Feedback in a simple Flashcard app, and I noticed an issue when it comes to the way the app functions that I don't really know if it's solvable, but thought I would share: Because of the way the issue was, the associated replay didn't even show the dialog portion, so the issue was actually untraceably from the UF. In this instance, it was also not a code error and so there was no way to actually see the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Where do I find the tags I send? Codeexport function sendFeedback(feedback: Feedback) {
const { name, email, message, reaction, category } = feedback
const eventId = Sentry.lastEventId()
const userFeedback = {
name,
email,
message,
associatedEventId: eventId,
captureContext: {
tags: [{ key: reaction }, { key: category }],
},
}
Sentry.captureFeedback(userFeedback)
// Sentry.setTag("user_reaction", reaction)
// Sentry.setTag("feedback_category", category)
}I recieved the feedback , however I want to see where I can find the tags ( reaction = happy , categroy = compliment ) but I did not find them :
I use both of : captureContext: {
tags: [{ key: reaction }, { key: category }],
},and Sentry.setTag("user_reaction", reaction)
Sentry.setTag("feedback_category", category)But I could not find the tags. |
Beta Was this translation helpful? Give feedback.
-
|
@alamenai check that you are passing export function sendFeedback(feedback: Feedback) {
const { name, email, message, reaction, category } = feedback
const eventId = Sentry.lastEventId()
const userFeedback = {
name,
email,
message,
associatedEventId: eventId,
- captureContext: {
- tags: [{ key: reaction }, { key: category }],
- },
}
Sentry.captureFeedback(userFeedback, {
+ captureContext: {
+ tags: { key: reaction, key2: category },
+ },
})
} |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @ryan953 . |
Beta Was this translation helpful? Give feedback.
-
|
Hi, i am sending feedback via API - it worked earlier but after few months of not receiving any feedbacks i tried it myself and i found out despite 200 response, the feedbacks are not displayed in the cloud sentry.io. Response 200 ok: Could anyone say what is wrong? I have checked as well the official Sentry postman collection again and it seems okay. Even after sending GET for feedbacks, they are not returned: |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately i have no link as the event is nowhere to be found - neither in the UI or API. All i have is the event id from the response. This is real one, 1 week old: As mentioned, i am not connecting the feedback with any other issue/event in sentry, we were using it as backend for our "feedback form" that any logged user could submit. |
Beta Was this translation helpful? Give feedback.
-
|
39e43a52e86a4fc6b007bfdd8c560f21
Have you created other feedback using the 39e43a52e86a4fc6b007bfdd8c560f21 event_id? |
Beta Was this translation helpful? Give feedback.
-
|
The /user-feedback/ endpoint is deprecated, though we still expect it to work here. https://docs.sentry.io/platforms/javascript/user-feedback/#user-feedback-api is the new method to send feedback. |
Beta Was this translation helpful? Give feedback.
-
|
I was able to find data on your report being submitted (ID 112142299), but not your event (39e43a52e86a4fc6b007bfdd8c560f21). Without the event feedback won't be created. Maybe there is an issue with the event IDs you are submitting? |
Beta Was this translation helpful? Give feedback.
-
|
Previously it was possible to create feedback in event, probably this is the cause of it - there is no event at all. Shall we continue in the issue so we do not duplicate comments here and there? :-) |
Beta Was this translation helpful? Give feedback.
-
|
It would be great if you could export user feedback. I've tried using Discover but it's appears to be using issuePlatform and doesn't show all the feedback shown in the feedback portal. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @djnugent -- thanks for sharing your feedback. What is your motivation/use-cade for exporting user feedback? |
Beta Was this translation helpful? Give feedback.
-
|
Id like to merge it other feedback sources (App Store, play store) so I can
have a unified feedback dataset. Which I’ll then use to analyze common
trends by using things like sentiment analysis.
Daniel
…On Wed, Sep 11, 2024 at 2:35 PM Jasmin ***@***.***> wrote:
Hey @djnugent <https://github.com/djnugent> -- thanks for sharing your
feedback. What is your motivation/use-cade for exporting user feedback?
—
Reply to this email directly, view it on GitHub
<#60134 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTLXO43XYIM7WYVEGFJUD3ZWCLO3AVCNFSM6AAAAAA7OZ5SKOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRRHA2DCNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @djnugent sorry for the late update but if you are still looking for a solution, maybe #80662 (comment) can help? |
Beta Was this translation helpful? Give feedback.
-
|
Most of the user reports have the default description - "Problem description" |
Beta Was this translation helpful? Give feedback.
-
|
This template looks like the result of custom code - check the callsites of the API fx, for your specific SDK platform. |
Beta Was this translation helpful? Give feedback.
-
|
@aliu39 we are using this template intentionally. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. I looked into it but not sure where the text is coming from. Can you create a ticket in your platform's SDK repo, explaining your setup? |
Beta Was this translation helpful? Give feedback.
-
|
@aliu39 thanks for the response. After some investigation we found that these messages are triggered by our internal automated test scripts. No problem in this functionality 😄 |
Beta Was this translation helpful? Give feedback.
-
The user feedback stops accepting the attachmentsI implemented a feature to let the users send a feedback a months, it was working and we where receiving screenshots ( images ). Today, while I was another feature that sends a specific feedback , I could not find the screenshots I send. When I checked the first feature and the feedback , I found that it stops sending the screenshots a while ago. This is the code: "use client"
import { useUser } from "@clerk/nextjs"
import { zodResolver } from "@hookform/resolvers/zod"
import * as Sentry from "@sentry/nextjs"
import { Bug, ImagePlus, Loader2 } from "lucide-react"
import { SyntheticEvent, useRef, useState } from "react"
import { useForm } from "react-hook-form"
import * as z from "zod"
import { Button } from "./ui/button"
import { Card, CardContent, CardDescription } from "./ui/card"
import { Form, FormControl, FormField, FormItem, FormLabel, FormMessage } from "./ui/form"
import { Input } from "./ui/input"
import { Sheet, SheetContent, SheetHeader, SheetTitle, SheetTrigger } from "./ui/sheet"
import { Textarea } from "./ui/textarea"
import { useToast } from "./ui/use-toast"
const propertyFeedbackSchema = z.object({
propertyName: z.string().min(1, { message: "Eigenschaftsname ist erforderlich" }),
currentValue: z.string().min(1, { message: "Aktueller Wert ist erforderlich" }),
suggestedValue: z.string().min(1, { message: "Vorgeschlagener Wert ist erforderlich" }),
description: z.string().optional(),
screenshot: z.instanceof(Uint8Array).optional(),
})
type PropertyFeedback = z.infer<typeof propertyFeedbackSchema>
export const BuildingDataFeedback = () => {
const { user } = useUser()
const { toast } = useToast()
const [sidebarOpen, setSidebarOpen] = useState(false)
const [isSubmitting, setIsSubmitting] = useState(false)
const screenshotInputRef = useRef<HTMLInputElement | null>(null)
const form = useForm<PropertyFeedback>({
resolver: zodResolver(propertyFeedbackSchema),
defaultValues: {
propertyName: "",
currentValue: "",
description: "",
suggestedValue: "",
},
})
const [previewUrl, setPreviewUrl] = useState<string | null>(null)
const handleFileChange = (event: SyntheticEvent<HTMLInputElement>, onChange: (value: Uint8Array) => void) => {
const { files } = event.currentTarget
if (files && files.length > 0) {
const reader = new FileReader()
reader.onloadend = async () => {
const buffer = await files[0].arrayBuffer()
const data = new Uint8Array(buffer)
if (data) {
onChange(data)
}
}
reader.readAsDataURL(files[0])
}
}
const sendFeedback = (feedback: PropertyFeedback) => {
if (user) {
const { fullName, emailAddresses } = user
const { propertyName, currentValue, suggestedValue, description, screenshot } = feedback
const eventId = Sentry.captureMessage("User Feedback")
if (fullName) {
const userFeedback = {
name: fullName,
email: emailAddresses[0].emailAddress,
message: `Eigenschaft: ${propertyName}\nAktueller Wert: ${currentValue}\nVorgeschlagener Wert: ${suggestedValue}\nBeschreibung: ${description}`,
associatedEventId: eventId,
}
if (screenshot) {
Sentry.getCurrentScope().addAttachment({
filename: `${propertyName}-screenshot.png`,
data: screenshot,
})
}
Sentry.captureFeedback(userFeedback)
Sentry.getCurrentScope().clearAttachments()
}
}
}
const handleUploadScreenshot = () => {
screenshotInputRef.current?.click()
}
const handleSubmit = async (formData: PropertyFeedback) => {
const data = formData
setIsSubmitting(true)
try {
sendFeedback(data)
setSidebarOpen(false)
form.reset()
// Clean up the preview URL
if (previewUrl) {
URL.revokeObjectURL(previewUrl)
setPreviewUrl(null)
}
toast({
title: "Feedback gesendet",
description: "Vielen Dank für Ihren Beitrag zur Verbesserung der Gebäudedaten.",
})
} catch (error) {
toast({
title: "Fehler beim Senden",
description: "Es ist ein Fehler aufgetreten. Bitte versuchen Sie es später erneut.",
})
// eslint-disable-next-line no-console
console.error("Error sending feedback:", error)
} finally {
setIsSubmitting(false)
}
}
return (
<Sheet
open={sidebarOpen}
onOpenChange={(open) => {
setSidebarOpen(open)
if (!open) {
form.reset()
}
}}
>
<SheetTrigger className='flex sticky bottom-6 justify-end'>
<Button className='rounded-full h-12 bg-red-500 hover:bg-red-600'>
<Bug size={20} className='mr-2' />
<span>Problem melden</span>
</Button>
</SheetTrigger>
<SheetContent side='right' className='w-96 p-0 sm:max-w-lg overflow-y-auto'>
<div className='p-6'>
<SheetHeader className='mb-6'>
<SheetTitle>Gebäudedaten korrigieren</SheetTitle>
</SheetHeader>
<Form {...form}>
<form onSubmit={form.handleSubmit(handleSubmit)} className='flex flex-col gap-4' autoComplete='off'>
<FormField
control={form.control}
name='propertyName'
render={({ field }) => (
<FormItem>
<FormLabel htmlFor='propertyName'>Eigenschaftsname</FormLabel>
<FormControl>
<Input id='propertyName' {...field} placeholder='z.B. Gebäudehöhe, Baujahr, usw.' />
</FormControl>
<FormMessage />
</FormItem>
)}
/>
<FormField
control={form.control}
name='currentValue'
render={({ field }) => (
<FormItem>
<FormLabel htmlFor='currentValue'>Aktueller Wert</FormLabel>
<FormControl>
<Input id='currentValue' {...field} placeholder='Aktuell angezeigter Wert' />
</FormControl>
<FormMessage />
</FormItem>
)}
/>
<FormField
control={form.control}
name='suggestedValue'
render={({ field }) => (
<FormItem>
<FormLabel htmlFor='suggestedValue'>Vorgeschlagener Wert</FormLabel>
<FormControl>
<Input id='suggestedValue' {...field} placeholder='Korrekter Wert' />
</FormControl>
<FormMessage />
</FormItem>
)}
/>
<FormField
control={form.control}
name='description'
render={({ field }) => (
<FormItem>
<FormLabel htmlFor='description'>Beschreibung (optional)</FormLabel>
<FormControl>
<Textarea
id='description'
{...field}
placeholder='Beschreiben Sie das Problem oder geben Sie weitere Informationen an'
className='min-h-24 resize-y'
/>
</FormControl>
<FormMessage />
</FormItem>
)}
/>
<FormField
control={form.control}
name='screenshot'
render={({ field }) => (
<FormItem>
<FormLabel>Screenshot (optional)</FormLabel>
<FormControl>
<div>
<Input
ref={screenshotInputRef}
type='file'
accept='image/*'
onChange={(event) => handleFileChange(event, field.onChange)}
hidden
/>
<Card
className='cursor-pointer hover:bg-slate-50 h-80 border-dashed border-2'
onClick={handleUploadScreenshot}
>
<CardContent className='relative flex flex-col justify-center text-center items-center p-4 mb-0 h-full'>
{field.value && field.value.length > 0 ? (
<div className='flex flex-col items-center gap-2 w-full'>
<p className='text-sm font-medium'>
{screenshotInputRef.current?.files?.[0]?.name ?? "Keine Datei ausgewählt"}
</p>
{previewUrl && (
<div className='mt-2 border rounded-md overflow-hidden max-h-80'>
<img
src={previewUrl}
alt='Vorschau'
className='object-contain max-w-full max-h-80'
/>
</div>
)}
</div>
) : (
<>
<ImagePlus />
<CardDescription className='text-xs mt-4'>
Laden Sie einen Screenshot des Problems hoch
</CardDescription>
</>
)}
</CardContent>
</Card>
</div>
</FormControl>
<FormMessage />
</FormItem>
)}
/>
<Button
type='submit'
className='absolute bottom-4 right-4 left-4 mt-4 h-11 rounded-full bg-blue-600 hover:bg-blue-700'
disabled={isSubmitting}
>
{isSubmitting ? (
<>
<Loader2 className='mr-2 h-4 w-4 animate-spin' />
Wird gesendet...
</>
) : (
"Korrektur vorschlagen"
)}
</Button>
</form>
</Form>
</div>
</SheetContent>
</Sheet>
)
}when I log the screenshot object , I find that it's not null:
Version: "@sentry/nextjs": "^8.27.0", UpdateIs that because we reached the size limit usage:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this, glad you were able to determine the root cause! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jas-kas , is it possible to send a Markdown template for the message property? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @alamenai, it's not possible today with a prebuilt widget; however you can provide this if you use your own form: https://docs.sentry.io/platforms/javascript/guides/nextjs/user-feedback/configuration/#bring-your-own-widget |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jas-kas , Yes I use my own form but when I send the message as Markdown, I received like a normal string. |
Beta Was this translation helpful? Give feedback.
-
New and Improved User Feedback - Beta Launch
While Sentry automatically detects errors thrown by your application, such as performance issues and user experience problems like rage clicks, there are other bugs your users may encounter (e.g., broken permission flows, broken links, typos, misleading UX, etc.). To identify and troubleshoot these cases quickly, we revamped our User Feedback product…
The new and improved User Feedback product is now available in beta to all Early Adopters. 🎉 🎉🎉 We would love for you to try it out and hear your feedback. To learn how to install User Feedback and customize the widget to match your application and needs, see here. Thank you all for your early feedback on our GitHub discussion a few months ago.
How it Works
The latest changes to User Feedback include an out-of-the-box web widget you can add on your application to collect user feedback at any time. This widget is compatible with all web platforms. If you’d like to use your own widget, see the instructions here.
Example of how the widget could look on your site.
When an end-user submits a feedback, we will then link that to available rich debugging context, including replays, errors, and tags such as URL, so you can get to the root of the problem faster. Check out this quick video demo for a walk-thru.
Example User Feedback Details page with Session Replay.
If you’ve set up Session Replay, you’ll be able to save more time and quickly understand the context of the user problem because you’ll be able to see exactly what they experienced before submitting their feedback. Note that Session Replay is not required to use this product.
Here are some functionalities you’ll see as part of the beta User Feedback product:
We Want to Hear Your Feedback
If you have any questions or concerns, please let us know. Once you’ve tried our new and improved User Feedback product, please share your feedback below. 👇
Note: If you are currently using our existing User Feedback product where we attach written user messages to Sentry issues, rest assured that this functionality will not be going away. New incoming submissions from this modal will live in the new UI we built for User Feedback shown above.
Beta Was this translation helpful? Give feedback.
All reactions