This article is for Tempo for Cloud.
Migrated worklogs: creation date, author and the REST API
When worklogs are migrated from Jira Data Center to Jira Cloud and synced to Tempo, Tempo keeps the original Jira creation date and the original work start date of each worklog. Tempo does not replace them with the migration date.
The worklog author from Jira is also kept, including for users who have since been deactivated, as long as Jira returns the author on the worklog.
Creating worklogs through the Tempo REST API
The Tempo REST API does not accept a creation date when a worklog is created. Creation time is set by Tempo at the moment the worklog is created. The only date you control is the work date, using startDate and startTime. Any created or createdDate value in the request body is ignored.
To bring historical worklogs into Tempo after a migration, use the Jira worklog sync rather than re-creating worklogs through the API. The sync keeps the original history. See Tempo and Jira worklog sync on Cloud and the Tempo API documentation.