Migration from Server/Data Center to CloudLearn about the migration of Smart Attachments for Jira. |
Please go through our step-by-step instructions to migrate the Smart Attachments app's data to Jira Cloud. Please address your questions or issues to our support .
The Smart Attachments for Jira app migrates only the data for the projects available in Jira Cloud. You need to migrate the app simultaneously with Jira projects. |
Before proceeding to migration of the Smart Attachments app from Jira Server/Data Center to Jira Cloud, please check Pre-Migration Assessment Checklist.
Please consider that the migration process can take up to 48 hours. |
Please note that the app prevents starting a new migration for the same host if another migration for it is in progress. |
You don't need to perform the re-index on Cloud. It starts automatically upon the end of migration
Labels are global. Please, follow the information in our documentation to learn how to start with an app and how to administer labels on Cloud.
This behavior can be caused by the fact that this particular Jira issue has access restrictions configured the attachment section. If Jira Field Configuration for some issue types in the migrated project has the attachment field set to hidden, then attachments still display on the issue view screen. However, hidden fields are not returned through the Jira API's. As soon as you change the field configuration to show the attachment field, the API call will return the expected result (with attachment data) and the Smart Attachments section within the impacted issues will correctly display the list of attachments.
Please, check for the scheme configuration in your Jira Server/Data Center in the projects where you have this issue. Our app doesn't migrate labels from the default Uncategorized category even if it has been renamed in your project. You can find more details in the migration documentation.
The migration process can take up to 48 hours. So, this is within the expected range.
The migration procedure of our app data and any other app data is a multi-step process requiring lots of inter-communication of a Server app, Cloud storage, app migration platform, and Jira Cloud. Please review the Atlassian documentation with the migration procedure described in the schemes for details.
Additionally, our app must run migration at a moderate speed to avoid rate limits. Another possible reason for the migration time increase is the situation of several simultaneous migrations performed at the same time, which results in the app migration queue.
This behavior can be caused by the lack of permissions for our app in a particular Jira issue. You'll see the message "Issue does not exist, or you do not have permission to see it."
If you have issue security levels configured, our app will lack permission to add labels in this project. You can resolve this issue by adding the project role atlassian-addons-project-access to the security level:
Select the atlassian-addons-project-access project role, then click the Add button.