add rage click issues #9268
add rage click issues #9268
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 1.34kB ⬆️
|
| In order to see rage clicks in your issue stream on the **Issues** page, your organization needs to: | ||
|
|
||
| - Be sending [session replay events](/product/session-replay/getting-started/) | ||
| - Enable the JavaScript SDK (or related framework), version 7.60.1 or higher |
There was a problem hiding this comment.
I think this is a little confusing because the javascript SDK docs say version 7.27.0 or higher. I'm also not sure if the same version applies to "related framework".
If the requirements are different for session replays and rage click issues, I think it would help to explicitly call that out.
There was a problem hiding this comment.
Great call! @jas-kas could you weigh in?
There was a problem hiding this comment.
nit: is "(or related framework)" the phrasing?
something like "(or framework specific bundle)" idk
i can confirm that you need sdk v7.60.1 to get rage clicks.
older versions of the sdk will enable session replay, but you will not get rage-click issues from those.
There was a problem hiding this comment.
^ +1 what Ryan said. You need to be on a newer SDK version for rage click issues.
Co-authored-by: vivianyentran <[email protected]>
Co-authored-by: vivianyentran <[email protected]>
There was a problem hiding this comment.
nit: spacing on the right edge of this is smaller than on the left
There was a problem hiding this comment.
nit: spacing on the right side of this image is smaller than on the left
| @@ -0,0 +1,33 @@ | |||
| --- | |||
| title: Replay Issues | |||
There was a problem hiding this comment.
Should we consider having this be called Rage Click Issues until we have more Replay Issues?
There was a problem hiding this comment.
Yes, I think it makes sense for now, until we have other replay issues.
|
|
||
| If you've enabled [Session Replay](/product/session-replay/), you'll be able to see rage click issues on the **Issues** page in Sentry. Rage clicks, a series of consecutive clicks on the same unresponsive element, are a sure sign of user frustration and most likely deserve your attention. | ||
|
|
||
|  |
There was a problem hiding this comment.
Instead of using an image that have replay issue search, could we instead have an Issue Details page of a rage click issue? If we did, we could highlight the embedded replay video :)
There was a problem hiding this comment.
We can pull a screenshot from our demo proj: https://sentry-test.sentry.io/issues/5014485689/?project=4506072436572160&query=is%3Aunresolved+rage&referrer=issue-stream&statsPeriod=7d&stream_index=0
| In order to see rage clicks in your issue stream on the **Issues** page, your organization needs to: | ||
|
|
||
| - Be sending [session replay events](/product/session-replay/getting-started/) | ||
| - Enable the JavaScript SDK (or related framework), version 7.60.1 or higher |
There was a problem hiding this comment.
^ +1 what Ryan said. You need to be on a newer SDK version for rage click issues.
Co-authored-by: Jasmin <[email protected]>
| @@ -0,0 +1,33 @@ | |||
| --- | |||
| title: Replay Issues | |||
There was a problem hiding this comment.
Yes, I think it makes sense for now, until we have other replay issues.
Co-authored-by: Liza Mock <[email protected]>
Added rage click as an issue under new replay issues category.
Closes issue: #9077