Table of Contents maxLevel 2 minLevel 2 outline true style none
| maxLevel | 2 |
|---|---|
| minLevel | 2 |
| outline | true |
| style | none |
...
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.
| Info |
|---|
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.
...
- Your Jira instance runs on version 8.14 or above.
- Your version of the Electronic Signatures plugin is 3.0.6-jira8 or above.
- You've looked through Atlassian's documentation about a Jira Cloud Migration Assistant.
- You are a Jira admin.
Before migrating
...
- 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 products@anovaappsanovaproducts@appfire.com or visit our Service Desk .