[WEB-8477] fix(api): filter "Updated At" by updated_at column, not created_at

[mguptahub]

Re-raise of #9323 by @sanjibani. That PR is technically ready but cannot merge — its CLA is unsigned. Opening from a covered account so the fix can land. Credit for the fix and the tests belongs to @sanjibani; please close #9323 as superseded by this one once merged.

Problem

filter_updated_at() passed created_at__date as the date term in both its GET and POST branches, so filtering by "Updated At" actually filtered on the creation date. Work items updated today but created earlier never appeared under Updated At → is → today, and the "Created at" / "Updated at" filters returned identical result sets.

This is the legacy issue_filters.py query-param path (pre-existing — present in v1.3.1, not a v1.4.0 regression).

Fix

-                date_term=f"{prefix}created_at__date",
+                date_term=f"{prefix}updated_at__date",

in both branches of filter_updated_at(), plus the unit tests from #9323.

Adjustments made while porting

Two small issues in the original patch:

1. test_get_method_targets_updated_at_column always failed. It asserted the exact key "updated_at__date", but date_filter()'s single-value branch appends a lookup suffix, producing updated_at__date__contains. Changed to match on the key prefix. (Confirmed: a bare date yields {'updated_at__date__contains': '2026-06-26'}, while ;after yields {'updated_at__date__gte': ...}.)
2. Added the missing trailing newline to the new test file.

Verification (local canary build, Django 5.2.15)

With 5 work items — one created 2020-01-01 but updated today, four created today:

Query	Before	After
?updated_at=2026-07-01;after	4 ❌	5 ✅ (includes the 2020-created row)
?created_at=2026-07-01;after	4	4 ✅ (unchanged)

Before the fix both returned 4 (identical sets — the tell-tale symptom). Unit tests: 5 pass, and 4 of the 5 fail with the source change reverted. ruff check + format clean.

Related

Part of WEB-8477 (canary bug sweep). Complements — does not overlap — the other two fixes:

• fix: cast avatar_asset to CharField to resolve mixed type errors in URL concatenation #9512 — Django 5.2 mixed-type FieldError (Bugs 1, 2, 3). Also blocked on an unsigned CLA.
• [WEB-8477] fix: created_at/updated_at filters return no work items #9513 — rich-filter created_at/updated_at date lookups (Bug 5). Different code path: this PR fixes the legacy ?updated_at= query param, [WEB-8477] fix: created_at/updated_at filters return no work items #9513 fixes the filters={"updated_at__exact":...} rich-filter path. Both are needed.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Fixed the “Updated At” filter so it correctly searches by issue update dates instead of creation dates.
  • Ensured filtering works consistently for single dates, multiple dates, and different request methods.
  • Empty “Updated At” filters now leave existing results unchanged.

[Copilot]

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

[makeplane]

Linked to Plane Work Item(s)

• (WEB-8477) Community Bugs

This comment was auto-generated by Plane

[coderabbitai]

📝 Walkthrough

Walkthrough

Corrects filter_updated_at to filter on updated_at__date instead of created_at__date, with regression tests covering GET, POST, CSV, prefixes, and empty input.

Changes

Updated-at filter correction

Layer / File(s)	Summary
Filter correction and regression coverage apps/api/plane/utils/issue_filters.py, apps/api/plane/tests/unit/utils/test_issue_filters.py	filter_updated_at now generates updated_at__date filters, with tests covering GET and POST inputs, CSV dates, prefixes, and empty parameters.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• makeplane/plane#9513: Updates related updated_at date lookup handling in IssueFilterSet.

Suggested reviewers: pablohashescobar

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the core fix: Updated At now filters on updated_at instead of created_at.
Description check	✅ Passed	The PR includes a clear problem/fix summary, testing details, and related references, though it doesn't use the exact template headings.
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/updated-at-filter-column

---

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.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/api/plane/tests/unit/utils/test_issue_filters.py (1)

24-25: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Assert the generated filters more precisely.

These checks only inspect key substrings; the all(...) assertions also pass for an empty dictionary. Assert that the expected keys and values are present so the tests cannot pass when filtering produces no or malformed entries.

Also applies to: 31-32, 38-39, 46-47

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/api/plane/tests/unit/utils/test_issue_filters.py` around lines 24 - 25,
Strengthen the assertions in the issue-filter tests around the generated filter
mapping, including the repeated assertion blocks at the referenced cases. Verify
the exact expected filter keys and their corresponding values, rather than
relying on substring checks or vacuous all/any assertions, so empty or malformed
filter dictionaries fail the tests.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/api/plane/tests/unit/utils/test_issue_filters.py`:
- Around line 24-25: Strengthen the assertions in the issue-filter tests around
the generated filter mapping, including the repeated assertion blocks at the
referenced cases. Verify the exact expected filter keys and their corresponding
values, rather than relying on substring checks or vacuous all/any assertions,
so empty or malformed filter dictionaries fail the tests.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 98dc8c4b-4bb2-4a0a-ac67-461a707fd7ca

📥 Commits

Reviewing files that changed from the base of the PR and between e496b24 and c547c85.

📒 Files selected for processing (2)

• apps/api/plane/tests/unit/utils/test_issue_filters.py
• apps/api/plane/utils/issue_filters.py