/
Jira Data Center not returning All Worklogs

Jira Data Center not returning All Worklogs

This issue affects Jira Data Center customers running Jira version 8.22.2 or later, particularly instances with issues containing a large number of worklogs.

Users may notice missing worklog records in calendars and reports because, starting from Jira 8.22.2, Jira indexes only the top N issue-related entities, including comments, change history entries, and worklogs.

Any operation that triggers a full issue reindex will reindex only a limited number of related entities. As a result, worklogs exceeding the configured indexing limit will not be available in JQL searches, reports, or apps relying on indexed data.

The default safeguard limits are documented here: https://support.atlassian.com/jira/kb/jira-indexing-limits-stats/

For Jira instances containing issues with a large number of worklogs, it is recommended to increase the default worklog indexing limit to ensure that apps such as Worklogs - Time Tracking and Time Reports have access to all required data.

The relevant system property is:

jira.safeguards.indexing.issue.worklogs

You can modify this value using the steps described in the Setting properties and options on startup documentation. For example, to increase the worklog indexing limit to 10,000 worklogs per issue:

JVM_SUPPORT_RECOMMENDED_ARGS="-Djira.safeguards.indexing.issue.worklogs=10000"

The optimal value depends on your reporting requirements and instance size. You can also set the property to -1 to disable the indexing safeguard entirely, although this may increase index size and reindexing time.

Without a full reindex, previously truncated worklogs may continue to be missing from JQL search results and reports. Please follow these steps:

  1. Update the JVM property on each Jira Data Center node.

  2. Restart all Jira nodes.

  3. Run a full foreground reindex.

  4. Verify that the reindex has completed successfully.