Issue Summary

The Issue Navigator search results show the DueDate value one day behind the actual value when using OpenSearch as the default search engine with TimeZone -03. It is possible that the bug affects other time zones.

Steps to Reproduce

1. Set up a Jira 11.3.7 test environment using PostgreSQL 17.

1. Set PostgreSQL's timezone to America/Sao Paulo by configuring the following: postgresql.conf parameters, then restart PostgreSQL:
    

log_timezone = 'America/Sao_Paulo' 
timezone = 'America/Sao_Paulo'

1. Set Jira's user timezone to America/Sao Paulo with the following startup parameter, then restart Jira:
    

   -Duser.timezone=America/Sao_Paulo

1. Create an issue with a due date (e.g. 2026-07-05).

1. Configure Jira to use OpenSearch as per [Configuring OpenSearch for Jira | Administering Jira applications Data Center 11.3 | Atlassian Documentation|https://confluence.atlassian.com/adminjiraserver/configuring-opensearch-for-jira-1620511851.html]
2. Reindex Jira or issue.
3. Perform a JQL to show an issue.

Expected Results

When viewing the search result, the Due (Due date) shows the same value as when viewing the issue under the view issue screen.

Actual Results

The search result, which gets the result from the Search Engine, in this case, OpenSearch, shows the result of Due (DueDate) one day behind the actual value:

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.