Skip to content

Conversation

@bruno-garcia
Copy link
Member

@bruno-garcia bruno-garcia commented Nov 21, 2023

Links to Widget and Crash Report (old Modal) are temporary until SDK docs move around.

Moved User Feedback up the menu to be below Session Replay.

Screenshots taken as-is from draft docs, @Jesse-Box @jas-kas are these good enough? If not could u give a hand on getting better ones?

Relates to: #8493

@vercel
Copy link

vercel bot commented Nov 21, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 4, 2023 11:59pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
sentry-docs-next ⬜️ Ignored (Inspect) Visit Preview Dec 4, 2023 11:59pm

Copy link
Contributor

@vivianyentran vivianyentran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added some suggestions but overall looks good!

Copy link
Contributor

@vivianyentran vivianyentran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, pending the decision on naming


## Where to View User Feedback

Whether you choose to collect user feedback via a Feedback Widget, a Crash-Report modal, or both, you’ll be able to view it from the **User Feedback** page. The page is chronologically-organized with the most recent, unresolved feedback at the top. You can click on individual feedback to see more details all in one view, similar to your e-mail inbox. The right-hand side shows the **User Feedback Details** view, which includes the user’s description and any available debugging context.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any differentiators between feedback from the form/widget and crash report in the UI? Or any way to filter for one or the other? If so, seems worthwhile to include that info.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point! There are differences indeed, lets expand

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could add to the bottom (after the last sentence in this heading:

Feedback collected via the Crash-Report Modal displays a crash-report label. And a link to the issue that resulted in the modal popping up.

Or something?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bruno-garcia ^ I like this!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I like that too!

Feedback collected via the Crash-Report Modal displays a crash-report label and a link to the issue that resulted in the modal popping up.

Would just make it one sentence instead of two.

But I'm not sure if I'm seeing the label correctly, as least in the demo app. It looks like this feedback has a linked issue but I don't see the label. Can you verify what it's supposed to look like?
https://demo.sentry.io/feedback/?feedbackSlug=android%3A4657517631&referrer=feedback_list_page&statsPeriod=7d

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's gone

@jas-kas
Copy link
Member

jas-kas commented Nov 22, 2023

Looks good to me!

Only a couple other things to note:

  • We'll need to update the links for configuration
  • Resize and replace some of the images and I'll also run them by Jesse

@bruno-garcia
Copy link
Member Author

IMO we just need improved images and we should be ready to merge this. We can iterate from there with improvements, including link to SDK docs (instead of npm/github) once #8528 is merged

@jas-kas
Copy link
Member

jas-kas commented Dec 1, 2023

@bruno-garcia Looks ready to ship! :shipit:

We'll need to follow up with a link to SDK docs here once they go live: "Learn more about how to install and customize it here."

@bruno-garcia
Copy link
Member Author

@jas-kas ready to merge anytime then. Holding it off until we have it open beta.

Added to: https://github.com/getsentry/team-replay/issues/273

@bruno-garcia bruno-garcia enabled auto-merge (squash) December 4, 2023 23:49
@bruno-garcia bruno-garcia merged commit afed2b0 into master Dec 4, 2023
@bruno-garcia bruno-garcia deleted the feat/user-feedback-product-docs branch December 4, 2023 23:57
@github-actions github-actions bot locked and limited conversation to collaborators Dec 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants