payloadcms / payloadcms/payload

Bug: blank options shown for timezone when adding filter on collection view

Open
#14,972 1 comment 1 reaction 1 assignee View on GitHub

@paulpopus is already working on this.

Since Dec 18, 2025.

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

Description

Describe the Bug

When adding a filter on the collection view, I am seeing blank options - which I assume to be the timezone from the date field.
Image

While this is a guess, I am fairly certain since after I select the blank option, time zones are shown as filter options
Image

Here is part of the collection config. There are no fields defined between startDate and endDate which further suggests the blank option is the timezone

export const startAndEndDateField = (): RowField => ({
  type: 'row',
  fields: [
    {
      name: 'startDate',
      type: 'date',
      timezone: {
        supportedTimezones: TIMEZONE_OPTIONS,
      },
      required: true,
      admin: {
        date: {
          pickerAppearance: 'dayAndTime',
        },
        width: '50%',
      },
    },
    {
      name: 'endDate',
      type: 'date',
      timezone: {
        supportedTimezones: TIMEZONE_OPTIONS,
        required: true,
      },
      admin: {
        date: {
          pickerAppearance: 'dayAndTime',
        },
        description:
          'Optional end date for multi-day events. Timezone will always be set to the startDate timezone.',
        width: '50%',
      },
...
Link to the code that reproduces this issue

https://github.com/NWACus/web/blob/main/src/fields/startAndEndDateField/index.ts

Reproduction Steps
  1. Navigate to collection with date field
  2. Select Filters
  3. Select first dropdown and see blank options
  4. (Optional) select blank option and see timezones in 3rd dropdown
Which area(s) are affected?

area: ui

Environment Info
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: 1.22.10
  pnpm: 10.6.4
Relevant Packages:
  payload: 3.66.0
  next: 15.5.7
  @payloadcms/db-sqlite: 3.66.0
  @payloadcms/drizzle: 3.66.0
  @payloadcms/email-nodemailer: 3.66.0
  @payloadcms/email-resend: 3.66.0
  @payloadcms/graphql: 3.66.0
  @payloadcms/live-preview: 3.66.0
  @payloadcms/live-preview-react: 3.66.0
  @payloadcms/next/utilities: 3.66.0
  @payloadcms/plugin-cloud-storage: 3.66.0
  @payloadcms/plugin-form-builder: 3.66.0
  @payloadcms/plugin-seo: 3.66.0
  @payloadcms/richtext-lexical: 3.66.0
  @payloadcms/storage-vercel-blob: 3.66.0
  @payloadcms/translations: 3.66.0
  @payloadcms/ui/shared: 3.66.0
  react: 19.1.0
  react-dom: 19.1.0

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.