---
title: "FAQ Electronic Signatures for Jira Cloud"
canonical: "https://support.appfire.com/space/ESF/17498212/FAQ%20Electronic%20Signatures%20for%20Jira%20Cloud"
format: markdown
---
> Macro (aura-html)

### Can I see signature information without expanding the panel?

Yes. Jira Cloud offers two display options for issue panels:

1. **Current view**: Panels are collapsed by default and require clicking to expand
2. **Legacy view**: Panels display information immediately without additional clicks

To access the legacy view, add `?oldIssueView=true` to your Jira URL. This will show signature information directly without requiring panel expansion.

### Why do I still see previous signatures after using the Revoke E-Signatures post function?

The **Revoke E-Signatures **post function clears signature requirements for workflow validation but preserves the signature history for audit purposes. This means:

- Previous signatures remain visible in the E-Signatures section.
- Signature requirements are reset for future workflow transitions.
- Users must provide new signatures to proceed to subsequent workflow states.

This design supports compliance documentation while ensuring fresh authorization for new workflow phases. The post function works optimally when combined with E-Signatures validators.

### Does Jira Cloud Electronic Signatures have the same features as the DC version?

We strive to maintain feature parity between Cloud and Server versions, but some differences can exist due to architectural distinctions between the platforms. Where applicable, cloud-specific limitations or enhancements are noted throughout this documentation.

The table below presents a feature comparison between Electronic Signatures for Jira DC and Jira Cloud. For the most current feature comparison and roadmap information, please contact our support team at **[support@appfire.com](mailto:support@appfire.com)**.

| **Feature** | **DC** | **Cloud** |
| --- | --- | --- |
| Bulk operation with Electronic Signatures | :check_mark: | :cross_mark: |
| Exception for Signing an Issue | :check_mark: | :cross_mark: |
| JQL functions | :check_mark: | :cross_mark: |
| Prevents unauthorized actions on tickets | :check_mark: | :check_mark: |
| Requesting a specific group or user to sign | :check_mark: | :check_mark: |
| Requiring Electronic Signatures on the ticket transition screen | :check_mark: | :cross_mark: |
| Signature information tab | :check_mark: | :check_mark: |
| Сheck user credentials before the transition is performed (ES Validator) | :check_mark: | :check_mark: |
| [Сompliant with FDA CFR 21 part 11](https://appfire.atlassian.net/wiki/download/attachments/17498212/Anova%20Electronic%20Signatres%2021%20CFR%2011%20Validation%20Report.pdf?version=1&modificationDate=1630927773806&cacheVersion=1&api=v2) | :check_mark: | :cross_mark: |