[WEB-8477] fix: created_at/updated_at filters return no work items

[mguptahub]

Problem (WEB-8477, Bug 5)

Filtering the work item list by a creation/update date returns no work items.

created_at / updated_at are DateTimeFields, but the UI sends a bare calendar date, and the filterset only exposed exact and range lookups. Both are wrong for a datetime column:

Request the UI sends	What the ORM did	Result
{"created_at__exact":"2026-07-30"}	coerced to 2026-07-30 00:00:00	matched only rows stamped exactly midnight → always empty
{"created_at__range":"2026-07-28,2026-07-30"}	upper bound capped at 2026-07-30 00:00:00	silently dropped everything created during the final day (only "worked" if you overshot the end date by a day)

Reproduced from the bug report's exact query strings on a local canary build — both returned total_count: 0 with 4 matching work items present.

Fix

Compare the date component instead, so a calendar date means the whole day and both range bounds are inclusive:

• created_at / created_at__exact → lookup_expr="date"
• created_at__range → lookup_expr="date__range" via a new DateCSVRangeFilter (BaseCSVFilter + DateFilter) that parses the UI's "a,b" CSV value
• same for updated_at

The UI's existing query format is unchanged — no frontend change needed.

Verification (local canary build, Django 5.2.15)

Query	Before	After
created_at__exact=2026-07-30	0	4 ✅
created_at__range=2026-07-28,2026-07-30 (report's case)	0	4 ✅
created_at__range=2026-07-30,2026-07-30	0	4 ✅
created_at__exact=2020-01-01 (backdated row)	0	1 ✅
created_at__range=2019-01-01,2019-12-31	0	0 ✅ (negative control)
updated_at__exact=2026-07-30	0	5 ✅ (incl. a row created in 2020 but updated today)

Adds plane/tests/unit/utils/test_issue_datetime_filters.py (7 tests). 6 of the 7 fail without this change (verified by reverting the fix); the 7th is a negative control that passes either way. ruff check + format clean.

Scope notes

• Pre-existing, not a v1.4.0 regression — filterset.py is byte-identical on master (v1.3.1).
• Not covered by fix: cast avatar_asset to CharField to resolve mixed type errors in URL concatenation #9512 (Django 5 mixed-type FieldError, which fixes WEB-8477 Bugs 2 & 3) or fix(api): filter "Updated At" by updated_at column, not created_at #9323 (the legacy issue_filters.py updated_at→created_at copy-paste bug). This is a third, independent cause.
• ⚠️ Known remaining issue, deliberately not fixed here: __date is evaluated in the active timezone, which TimezoneMixin takes from the user's profile (user_timezone) rather than the browser's timezone. A user whose profile timezone differs from their browser can still see off-by-one-day results (verified: same data returns different rows for user_timezone=UTC vs Asia/Kolkata). Needs a product decision on which timezone is authoritative, so it's tracked separately.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Improved issue date filtering for creation and update dates.
  • Exact-date filters now include all issues from the selected calendar day, regardless of time.
  • Date-range filters now include the full final day and exclude issues outside the selected range.
  • Added regression coverage to ensure consistent filtering behavior.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d9a7625b-ff80-4658-80b0-9d4d1281e1c0

📥 Commits

Reviewing files that changed from the base of the PR and between 7564480 and 79f5529.

📒 Files selected for processing (2)

• apps/api/plane/tests/unit/utils/test_issue_datetime_filters.py
• apps/api/plane/utils/filters/filterset.py

---

📝 Walkthrough

Walkthrough

Issue datetime filters now interpret UI-provided dates as calendar-day values for exact and inclusive range lookups. New unit tests cover created_at and updated_at filtering across matching and non-matching dates.

Changes

Issue datetime filters

Layer / File(s)	Summary
Calendar-day filter implementation apps/api/plane/utils/filters/filterset.py	Adds DateCSVRangeFilter and changes issue created_at and updated_at exact/range filters to use date-component lookups.
Calendar-day filter regression tests apps/api/plane/tests/unit/utils/test_issue_datetime_filters.py	Adds controlled timestamp fixtures and tests for exact-day matching, inclusive final days, and exclusion of dates outside the requested range.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: dheeru0198, pablohashescobar, copilot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: fixing created_at/updated_at filters returning no work items.
Description check	✅ Passed	The description is detailed and mostly follows the template, covering the problem, fix, verification, and references.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch web-8477/canary-bug-fixes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[makeplane]

Linked to Plane Work Item(s)

• (WEB-8477) Community Bugs

This comment was auto-generated by Plane