| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
The post function cleans signatures from workflow status and does not delete any information from E-Signatures tab or Issue glance. This means that your signature will be required again when you try to make transition to a certain state. This is helpful to use the E-Signatures post function along with using the E-Signatures validator.
Can I expect that the Cloud version has the same functionality as the Server version?
We're working hard to ensure the most similar functionality in Cloud as you're used to seeing in Server. But it may not be totally the same due to different architecture between Server and Cloud Jira versions.
Feature | Server/DC | Cloud | Note |
|---|---|---|---|
| Bulk operation with Electronic Signatures |  |  | Scheduled |
| Exception for Signing an Issue | | | Scheduled |
| JQL functions | | | Investigating feasibility |
Prevents unauthorized actions on tickets | | | |
| | Investigating feasibility | |
Requiring Electronic Signatures on ticket transition screen | | | This functionality is not relevant in Cloud |
| Signature information tab | | | |
| Сheck user credentials before the transition is performed (ES Validator) | | | |
Сompliant with FDA CFR 21 part 11 | | |
I have another question, where do I get help?
...