Open dachakra opened 2 days ago
Routing to @getsentry/product-owners-dashboards for triage ⏲️
Routing to @getsentry/product-owners-discover for triage ⏲️
Assigning to @getsentry/support for routing ⏲️
This makes sense, thanks for raising! I'll add this to our backlog. Aside: this is a good thing to do when we standardize column rendering for table widgets.
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
For example;
Looking at the following discover query:
The goal is to retrieve an event with tag
customerType:large
when clickling issue URLREACT-4SM
. But upon clicking on the first entry, the search condition detail is lost in the issue details page: (noticecustomerType:small
)Expected Result
We expected functionality tobe similar to the issue stream.
For example; Searching for
customerType:large
in the issue stream returns the following:When opening an issue, the search condition is preserved and the right event is
Actual Result
Product Area
Discover
Link
No response
DSN
No response
Version
No response