Missing worklogs

Owned by Kamil Parzyjagła
Last updated: Oct 02, 2024 by Anna Kwaśny
3 min read

 When using Worklogs, you rarely might encounter inconsistencies between the logged time and the actual results.

  1. If it happens, first of all, make sure that the filters are correct. For example, you could have selected a user that hasn’t logged any time.

  2. If work logs for a certain project are missing, there is a big chance that you have hidden the log work field in the settings (it's visible in the issue screen but not to us). To solve this, follow these steps:

    1. Click Jira settings (Cloud) or Jira administration (Server) → Issues → Field Configuration under the 'Fields' section.

    2. You will see your field configurations here. Click the one that is associated with the project with missing work logs. Find 'Log Work' field and click the Show button on the right.

Cloud:

Server:



Index Safeguards adjustment

 

Affects Server/Data Center customers on version 8.22.2 or higher, with a large number of worklogs in issues.

 

Users using Jira Server or Data Center version might notice some of the data missing from their reports. Starting from 8.22.2 Jira indexes only the top N of the following issue-related entities: comments, change history, and worklogs.

Any operation that triggers full issue re-index will re-index a limited number of related entities like worklogs and the remaining ones won’t show in reports. The default limits are listed here: Introducing Safeguards for Jira index

 

For instances that have issues with larger amount of worklogs it’s recommended to tweak the default indexing limit to ensure that Worklogs - Time Tracking and Time Reports has access to all the required data.

The system property name is as follows: jira.safeguards.indexing.issue.worklogs

 

You can use the steps described in the Setting properties and options on startup article to change the values. For example, limit the number of indexed worklogs to 10000 per issue.

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

The exact number depends on your reporting needs and can be set to -1 if you want to disable index safeguards completely.

Do you have any questions or feedback? Feel free to contact us here