payloadcms / payloadcms/payload

“Equals” filter on updatedAt field doesn’t return results when selecting the same date via DatePicker

Open
#12,413 6 comments 0 reactions 1 assignee View on GitHub

@paulpopus is already working on this.

Since Jun 16, 2025.

Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Description

Describe the Bug

The native “equals” filter for the updatedAt field (and other date fields) fails to match documents when I pick the same date shown in the document list. Even though the calendar picker and the list display the identical date (e.g. 2025-05-14), no documents are returned.

Link to the code that reproduces this issue

https://github.com/matteo-naif/payloadcms-test-date-filter

Reproduction Steps
  1. Navigate to a collection in Payload CMS that includes an updatedAt timestamp field.
  2. Open the list view for that collection.
  3. Note a document’s “Updated At” date (for example, May 14, 2025).
  4. Click “Add Filter”, choose the updatedAt field, select the “equals” condition.
  5. Use the date picker to select the exact same date displayed in the list (2025-05-14).
  6. Apply the filter.
Which area(s) are affected? (Select all that apply)

area: core

Environment Info
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  payload: 3.37.0
  next: 15.3.0
  @payloadcms/db-mongodb: 3.37.0
  @payloadcms/email-nodemailer: 3.37.0
  @payloadcms/graphql: 3.37.0
  @payloadcms/next/utilities: 3.37.0
  @payloadcms/payload-cloud: 3.37.0
  @payloadcms/richtext-lexical: 3.37.0
  @payloadcms/translations: 3.37.0
  @payloadcms/ui/shared: 3.37.0
  react: 19.1.0
  react-dom: 19.1.0
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.4.0: Fri Apr 11 18:33:47 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.