search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.1k stars 4.2k forks source link

First Seen sort doesn't work when filtering by some issue states #52398

Open brianthi opened 1 year ago

brianthi commented 1 year ago

When filtering by is:ongoing or is:regressed, and sorting by first seen, the sort no longer works.

Image

snigdhas commented 1 year ago

I see the same issue for is:new

image

and is:assigned

image

This seems broken for is:xxx filters where xxx isn't one of the predefined tabs, as well as last_seen on Unresolved and first_seen on the Regressed tabs.

snigdhas commented 1 year ago

From this thread, the first_seen discrepancies should be fixed once first_seen is added to clickhouse. The last_seen discrepancies may be fixable if we fetch the value from buffers in the serializer. last_seen changes too frequently for us to store it in clickhouse.

NandoZee commented 1 year ago

Same issue here. Is "adding to clickhouse" something users can do, or is that a feature yet to be released?

getsantry[bot] commented 1 year ago

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

malwilley commented 1 year ago

Same issue here. Is "adding to clickhouse" something users can do, or is that a feature yet to be released?

@NandoZee this is a functionality we are actively working on - no need for any user configuration!

ludoframer commented 3 months ago

I have the exact same issue. "Last Seen" works well, but "First Seen" is just random ordering

notes: I removed all filter just in case, but still the same issue

b-hayes commented 2 months ago

The same experience here doesn't work no matter what I do. I need it to work right now too. Real pain in the neck.

JoshFerge commented 2 months ago

We are currently rolling out a bigger change that should fix this -- will update when we're completely rolled out. thanks all!

b-hayes commented 2 months ago

We are currently rolling out a bigger change that should fix this -- will update when we're completely rolled out. thanks all!

How much longer do we need to suffer? its big problem. I got some major platform upgrades in the comming weeks and not being able to see the new vs old issues will be an absolute nightmare.

There WILL be a LOT of them and I need to prioritize.

snigdhas commented 2 months ago

Hi @b-hayes, I understand your frustration. We've fixed this as part of a larger effort to improve the search accuracy and performance and are fixing a final few bugs before we role it out. In the meantime, I'd suggest trying to search for is:new to see issues that were created in the past 7 days. It's not a perfect solution but we should have this fix out in the next couple of weeks. You can enable organization’s Early Adopter status to get the fix asap.

b-hayes commented 2 months ago

@snigdhas is:new helps a lot thanks!