Skip to end of banner
Go to start of banner

ES Cloud - Migration from Server/DC to Cloud

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Introduction

Electronic Signatures app is a powerful tool to prevent unauthorized actions on Jira issues and save your data. We realize that no changes should ruin your compliance with the FDA regulation CFR 21 part 11. That's why we're doing our best to make your path from Server / Data Center to Cloud easy and smooth. You should not worry about losing your data due to moving to a new environment. In cooperation with the free Atlassian plugin, we ensure a fast and robust mechanism to move your electronic signatures to the cloud instance. No extra effort or cost.

Electronic Signatures Server vs Cloud

Differences in Electronic Signatures Server and Cloud

We're working hard to ensure the most similar functionality in Cloud as you're used to seeing in Server. But there are some differences due to the absolutely different architecture between Server and Cloud.  The good news is core functions and usability are the same.

Due to different architecture between Server and Cloud Jira versions, the app functionality is not totally the same. See more in the comparison table here.


What data is migrated?

We provide the ability to migrate the full history of executed electronic signatures. Records from the Electronic Signatures tab will be available on your cloud site as you're used to seeing them in Jira server.


Prerequisites for migration

  1. Your Jira instance runs on version 8.14 or above.
  2. Your version of the Electronic Signatures plugin is 3.0.6-jira8 or above.
  3. You've looked through Atlassian's documentation about a Jira Cloud Migration Assistant. 
  4. You are a Jira admin.


Before migrating

  1. Install Electronic Signatures plugin or re-install it if you already have it on your Jira Cloud site. You have to re-install the app only once, before your first Electronic Signatures app migration. 

  2. On Server, enable feature flags for app migration in the server instance of Jira. Use the following link <Jira_URL>/secure/SiteDarkFeatures!default.jspa and add com.atlassian.jira.migration.app-migration.feature to Site Wide Dark Features if it is absent.



  3. Default Loggers section click Configure logging level for another package and add necessary packages with Track level:

    • ru.andreymarkelov.atlas.plugins.cfr.listener.CloudMigrationProcessListener
    • ru.andreymarkelov.atlas.plugins.cfr.service.CloudMigrationService



Migration process

When all prerequisites are met, you are able to migrate your data from Server/DC to Cloud. 

Steps to follow to migrate from Jira Server or Data Center to Jira Cloud:

  1. To migrate data, go to Jira Administration settings in Jira Server → System → Import and Export section→ Migrate to cloud.




  2. Select Assess and Install apps and mark the Electronic Signatures app as Needed in cloud.



  3. Perform steps according to Assessment wizard.


     

  4. Go to Manage your migration and click Create new migration button.




  5. On the next page, you may find a short Atlassian explanation about the migration steps. Click Connect to cloud to continue.




  6. Specify the name of migration and your cloud site, so that to connect your Server and Cloud instances.


    You need to be an admin in both your server and the destination cloud sites. If you have already connected a cloud site, you should see it in the dropdown. 

    If your Jira Server site is behind a firewall, you'll need to allow access to the domain: atlassian.com. You also might need to allow access to other Atlassian domains. 

  7. Depending on whether the appropriate projects already exist in the cloud, choose which data to migrate. You can transfer Electronic Signatures plugin data during or after the project migration. 



    If you have already moved your project to the cloud before, click 'I don't intent to migrate projects' and select Users and groups only. In this case, Electronic Signatures history regarding tickets that are existed in cloud will be migrated.

  8. You can choose to migrate all or some of your projects. You won’t be able to migrate projects with project keys that already exist in your Jira Cloud destination site.




  9. Choose how you want to migrate users and groups. Learn more about user and group migration.




  10. Make sure you marked the Electronic Signatures app as Needed in cloud to migrate the application data.



  11. In the next step, Jira Cloud Migration Assistant will perform checking and notify you if there are any warnings or blockers for migration data from Server to Cloud.




  12. Carefully read and evaluate all the warnings, if any, before starting the migration. If you decide to Continue and fix later, you can come back to view the errors once you have saved your migration.




  13. After you click Run, the process will start and you will be able to see progress and migration status on the Migration dashboard. It takes some time, depending on your data size.



  14. You can view the project on your cloud site as soon as all the project data is migrated. 

    Note, depending on the size of migrated projects and other data, it may take some time to start displaying Electronic Signatures history in the issues.


  15. Currently, Atlassian's logs migration reports do not include information about plugins' data. We recommend downloading and checking Jira logs manually. To check Jira logs, go to Jira Administration → System →  Troubleshooting and support tools.




  16. On Create support zip tab, click Customize zip and select from the list Jira application logs.




  17. In the downloaded file, you can find information about the migration result.





After migrating

Note, due to Jira Cloud Migration Assistant plugin limitations some data can't be migrated for now. We do monitor Atlassian's updates and will improve the migration of Electronic Signatures app as soon as the limitations are gone.


What you have to consider to keep enjoying Electronic Signatures plugin and stay safe in a new environment:

  • Electronic Signatures validator and post function can't be migrated and their purposes are slightly different in cloud. Read our documentation carefully and reconfigure them.
  • Migrated history of signatures does not contain names of Electronic Signatures custom field (User Validator, Logged User Validator fields) as they are not available in cloud.


If you have any questions or need assistance, contact the Anova Apps Products team at anovaproducts@appfire.com or visit our Service Desk .

  • No labels