Issue Summary

When migrating Jira projects from Jira Server/Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), worklogs are parsed and exported by JCMA, and the issue History / Changelog records the time spent increments and worklog IDs. However, the physical worklog entries are dropped / not inserted into the Jira Cloud worklog database table during Cloud batch ingestion.

As a result:

• The worklogs do not appear in the Jira Cloud issue view or worklog tabs.

• REST API queries to the issue metadata (GET /rest/api/3/issue/{key}?fields=worklog) show the correct non-zero total count from migration (e.g. total: 661), but calling the dedicated worklog endpoint (GET /rest/api/3/issue/{key}/worklog) returns an empty array (worklogs: [], total: 0).

• Monthly timesheet, billing, and worklog reports in third-party or native reporting tools fail to retrieve any worklog entries.

Steps to Reproduce

1. Migrate a Jira Server/Data Center project with extensive worklog history using JCMA.

1. Confirm that JCMA exports worklogs in the migration payload and completes with SUCCESS.

1. Open an affected migrated issue in Jira Cloud and inspect the Worklog tab / Issue History.

1. Call GET /rest/api/3/issue/{key}/worklog via REST API.

Expected Results

All worklogs exported from Server/DC are inserted into the Jira Cloud database and visible via UI and REST API.

Actual Results

• Issue history reflects that time spent was added with corresponding Worklog IDs, but the Worklog panel is empty.

• GET /rest/api/3/issue/{key}/worklog returns 0 worklogs.

• JCMA migration logs show no errors or warnings during container ingestion.

Workaround

Currently, there is no direct self-serve workaround. A backend database backfill / data fix script executed by Atlassian Database Operations / Engineering is required to re-insert the missing worklogs from the migration export payload into the Cloud tenant database.