Resolve missing attachments when migrating to cloud via Jira Cloud Migration Assistant
プラットフォームについて: Cloud および Data Center - この記事はクラウドと Data Center 両方のプラットフォームに等しく適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
The Jira Cloud Migration Assistant helps you move projects, users, and groups from Jira Server to Jira Cloud. When migrating Jira projects via the migration assistant, sometimes attachments are found missing from issues in the destination cloud site. This is because the attachments were possibly missing from the server instance in the first place. Either the attachment file was manually deleted or there was an error in removing the record of the attachment from Jira.
この記事では、添付ファイルが不足しているときの回避策をご案内します。
診断
The following error will appear in atlassian-jira.log
[INFO] [talledLocalContainer] 2023-03-31 09:36:53,627 pool-12-thread-16 INFO [c.a.j.m.workers.attachments.AttachmentMigrator] 8977319f-561e-48bc-b770-e73a65c558b7-jiraAttachmentUpload#8545caad-24f1-3d78-8d15-f449b58748bf$809d009b9c5f4ac4867d563abd9b87dbeae40bee294e439a8cfdb02487ef3104: initiating attachments sequence for project key ABC complete
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,016 pool-12-thread-16 INFO [c.a.j.m.workers.attachments.MediaUploader] Uploading attachments for project key=ABC, count=0
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,120 AttUpload-Thread-ABC-318 INFO [c.a.j.m.workers.attachments.AttachmentMigrator] no data for attachment 10035, ignoring
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,254 AttUpload-Thread-ABC-319 INFO [c.a.j.m.workers.attachments.AttachmentMigrator] no data for attachment 10300, ignoring
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,254 pool-12-thread-16 INFO [c.a.j.m.workers.attachments.MediaUploader] Uploading attachments done projectKey=ABC
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,256 pool-12-thread-16 WARN [c.a.j.migration.log.ExportLog] 2023-03-30 22:36:54.255 WARNING ABC attachment-export Found 2 missing attachments. Run the Instance Health check and fix all errors before migrating.
ソリューション
クラウドへの移行前に問題を解決するには、次の手順を行います。
Open the Jira log file. Learn more about how to work with Jira logs.
Search for the keyword
no data for attachment
Search for the log line
[INFO] [talledLocalContainer] 2023-03-31 09:36:54,120 AttUpload-Thread-ABC-318 INFO [c.a.j.m.workers.attachments.AttachmentMigrator] no data for attachment 10035, ignoring
Use the following query to retrieve details of the missing attachment by querying the Jira database:
AttachmentDetailsByProjectAndIssueselect fileattachment.filename, project.pkey, jiraissue.issuenum from fileattachment join jiraissue on fileattachment.issueid=jiraissue.id join project on jiraissue.project=project.id where fileattachment.id=10035;
Verify if the attachment exists in Jira.
If the attachment file is still available, upload it as a new attachment to the issue.
If the attachment is missing and can't be recovered, simply delete it from the issue.
Use the Jira Cloud Migration Assistant to restart the migration.
After the migration is done, contact support to cross-check the attachments.
It is recommended that you fix the issue when it is first detected in the Jira Cloud Migration Assistant. If you discover missing attachments after you have already migrated to Cloud, contact support to resolve this.