Issue Summary

When using searchType: date on a nested property of a type: object Forge custom field (jira:customFieldType), datetime values in ISO 8601 format (e.g. 2025-05-21T04:15Z) are silently not indexed and therefore not searchable via JQL. Only plain date values (YYYY-MM-DD) are indexed correctly. This behaviour contradicts the official Forge manifest documentation, which explicitly states that datetime format ([YYYY][MM][DD]T[hh]:[mm] with optional UTC offset) is supported for searchType: date.

Steps to Reproduce

• Create a forge app with manifest.yml looks like below

  jira:customFieldType:
      - key: customFieldType
        name: testDate
        render: native
        type: object
        formatter:
          expression: "`${value.testDate}`"
        schema:
          properties:
            testDate:
              type: string
              searchType: date
              searchAlias: testDate

• Set the Forge custom field value as below.

  {
        "value": "2026-05-26T13:24-05:00"
    }

• Search with below JQL

  customfield_10833.value is not EMPTY

Expected Results

Work item containing date time to be visible in the search result

Actual Results

Work item is not visible in the search result.

Workaround

Strip the time component from the stored value and use only the plain date format (YYYY-MM-DD). For example, store

{"value": "2025-05-21"}

instead of

{"value": "2025-05-21T04:15+02:00"}

. This limits the field to date-level precision but enables JQL search functionality.