getsentry / getsentry/sentry

Filter issues by when they were resolved

Open
#121,547 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Support filtering issues by resolve time (for example "resolved in the last 24h/7d"), not only by current status.

Current behavior

  • Issue search supports is:resolved for currently resolved issues
  • Age-related filters cover creation/activity only: age / firstSeen (when the issue was created) and lastSeen (last error event)
  • There is no public issue search field for resolve time (for example resolvedAt / statusChanged)
  • Docs: https://docs.sentry.io/concepts/search/searchable-properties/issues/

Gap

  • Teams building dashboards and triage views can bucket issues by creation age, but cannot answer "what was recently resolved"
  • is:resolved alone returns the full resolved set with no "recently" window
  • lastSeen and age are poor substitutes because they do not mean resolve time

This limits Issues search and Issues-dataset dashboard widgets that need a recently-resolved breakdown.

Requested by Anthony Yiannakou.

--

View Junior Session [Sentry]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the searchable-properties issues documentation and compare the existing is:resolved, age, firstSeen, and lastSeen filters. Trace how issue search and Issues-dataset dashboard widgets expose these fields. Done means users can filter resolved issues by a resolve-time window such as 24 hours or 7 days, with the public search documentation updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, backend-api-design, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.