Broken error link in transaction detail page

[smeubank]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

https://steven-eubank.sentry.io/performance/galloway-farms-nextjs:415374e688ba4834bf5f0b9922b1b9f6/?project=4504882863734784&query=&statsPeriod=14d&transaction=%2F#span-90b030d064358fae

DSN

No response

Steps to Reproduce

1. any transaction which is linked to a trace (at least I saw multiple examples of this)
2. navigate to the transaction detail page, the red banner should appear that says there is a linked error
3. try to click on it, it does nothing

(UX/UI feedback I always find the big red banners to look like something is wrong with my event, as in I did something wrong, and really it is just a link to)

Also I was slightly confused at first since the red banner at the top says pageload then when expanding the span with an error below it says network error

Expected Result

Link works and takes me to the error issue page

Actual Result

[getsantry]

Assigning to @getsentry/support for routing, due by Tuesday, April 4th at 5:00 pm (sfo). ⏲️

[getsantry]

Routing to @getsentry/performance for triage, due by Wednesday, April 5th at 17:00 (yyz). ⏲️

[0Calories]

Hey @smeubank,

The link in the red banner on the top calls out the specific span that captured the error event. In this case, it happens to be on the pageload span, and the error details themselves are on the span. You can still click on the error in the span details to go to the error issue page.

There actually is a regression here that occurred when I virtualized the span tree; The link at the top used to cause your browser to jump to the specific span with the error event, but it's not working now. It's a known issue, I just haven't had a chance to get around to fixing it yet 😄

Thanks for reporting this, I can keep you posted when it's fixed

[getsantry]

Routing to @getsentry/product-owners-performance for triage ⏲️

[gggritso]

@smeubank now that Sentry has an all-new trace view, is this still an issue?
cc @0Calories

[0Calories]

@gggritso We can close this, the new trace view doesn't have this problem