Sort issues feed by ingestion date

Allow sorting/filtering the Issues feed by ingestion (received) time, not only by event occurrence time.

Current behavior

• Issue feed sort options are Recommended, Last Seen, First Seen, Trends, Events, and Users (docs).
• Last Seen / First Seen are driven by the event occurrence timestamp (timestamp), not when Sentry received the event.
• Delayed delivery is common with offline/queued clients (e.g. Electron offline crash support). Events keep the original crash time and are sent later, so newly ingested activity can sort far down the feed.
• Events already expose server receive time at the event level (dateReceived / received), but that is not available as an Issues feed sort/filter.

Gap

Teams triaging offline or high-latency clients often care about "what just arrived in Sentry" for review queues. Occurrence-based Last/First Seen is still correct for when the crash happened, but it makes the Issues feed a poor inbox for newly ingested delayed events, especially when they attach to existing issue groups.

Related

• Historical: https://github.com/getsentry/sentry/issues/2702 (closed; track received vs occurred timestamp)
• Related latency case: https://github.com/getsentry/sentry/issues/85316

Requested by Wassim.

--

View Junior Session [Sentry]

Start with the Issues feed sorting described in the linked product documentation and compare it with the event-level dateReceived/received data mentioned in the issue. Review historical issue #2702 and related issue #85316 for prior context. Done means the feed can sort or filter by ingestion time while preserving the existing occurrence-time options.