...
When importing worklogs via Jira CSV import, our system relies on periodic syncing to detect and incorporate newly created worklogs in Jira. This is because, during Jira CSV imports, our system isn’t automatically alerted by Jira.
The missing notification from JIRA may occasionally introduce a delay of up to 24 hours before worklogs are visible in Tempo. It’s important to note that the delay isn’t solely dependent on the number of worklogs being imported but can be affected by it.
For customers handling substantial worklog imports, we offer the option to initiate a worklog sync reset, which triggers the synchronization of all worklogs starting from the beginning of time. This can be helpful in cases where customers are migrating from Server/DC Data Center to Cloud or importing data originating outside of Jira.