In case you haven’t heard, Atlassian recently announced that they’re accelerating the journey to Cloud with the end of life plan for Server. To help you best strategize your product transitions to Cloud, we want to familiarize you with the feature similarities and differences for Electronic Signatures.
FEATURE |
SERVER / DC |
CLOUD |
NOTES |
|---|---|---|---|
| Prevents unauthorized actions on tickets |
● |
● | |
| Exception for Signing an Issue | ● |  |
• Scheduled |
| Requiring Electronic Signatures on the ticket transition screen | ● | X | • This functionality is not relevant in Cloud |
| Bulk operation with Electronic Signatures | ● | |
• Scheduled |
| Signature information tab | ● | ● | |
| Сheck user credentials before the transition is performed (ES Validator) | ● | ● | |
| Requesting a specific group or user to sign | ● |  |
• Investigating feasibility |
| JQL functions | ● | |
• Investigating feasibility |
| Сompliant with FDA CFR 21 part 11 | ● | ● |
Review the feature comparisons of our other apps available on Cloud:
– Power Scripts™ for Jira
– Surveys for Jira
– Issue History Collector
Download a free Electronic Signatures trial today, and we will be announcing new Cloud features in the future. Stay tuned!
Tagged with: bulk operations, ES Validator, FDA CFR 21 part 11 compliant, prevent unauthorized actions, signature information tab, user credentials
Categorized in: Automation, Cloud, Data, Issue Template Automation, JQL Functions, Validators
