"Consent" means to give permission; "Approve" means to agree or accept as satisfactory. If your organization distinguishes the two, the Approval Path lets you model that distinction so it maps to your existing processes. From a technical perspective, the app treats approval and consent identically.

Work item field steps pick the approver(s) from a field on the work item.

A field doesn't need to be placed on a specific Jira screen to be selectable, but it must meet the following three conditions.

You can verify these in your Jira settings (Work items> Fields):

1. Matching Type: The field type must match the step.

• User steps require User Picker fields.

• Group steps require Group Picker fields.

• Email steps require Text fields.

2. Assigned Scheme: The field must be assigned to an active Configuration Scheme (e.g., the Default Configuration Scheme).

3. Correct Context: The field context must be set to Global, or explicitly include the space associated with your approval path.

First check your SMTP/email settings and the recipient's spam folder. If it happens only for a specific approval path definition, try recreating that definition. If it still persists, contact support.

Go to settings → JSM tab → Approval Path in JSM Customer Portal, and switch the option off. If the tab still appears after saving, try saving again, or report it to support.

Yes. You can completely automate your approval workflows using several methods:

• Workflow Transitions: Link the Approval Path to a specific Jira transition using a post-function so it triggers automatically.

• Jira Automation: Use the native "Start approval" action in your automation rules to launch definitions based on specific conditions, such as approaching due dates.

• REST API: Generate an API key in the app to programmatically create and manage approval paths via Web API calls.

• Webhooks: Set up event-based HTTP webhooks to receive real-time notifications, or use Incoming Webhooks to seamlessly trigger external system actions and fully hands-off workflows.

Those are handled by Atlassian, not by us. Please contact Atlassian support (https://support.atlassian.com/ ) or your solution partner. As Marketplace vendors, we don't control these matters.

1. Contact Atlassian to request the extension.

2. Request the extension from us by email (contact@warsawdynamics.com) or via the support portal.

3. Send Atlassian proof of our approval (usually a screenshot).

Email us at contact@warsawdynamics.com or use the support portal with: app name, end-customer name, SEN (Entitlement Number), Cloud site URL, renewal term (12 or 24 months), and partnership type. We process the request once the partnership is confirmed.

Yes. Our apps are SOC 2 Type II certified for the Security category, audited by Johanson Group LLP, with all controls operating effectively and no exceptions noted during the audit period.

→ Security

Our Cloud apps run on OVH Cloud infrastructure in Poland (EU). Encrypted backups are stored in Wasabi with restricted access. → Subprocessors

Data is encrypted in transit via HTTPS/TLS, and backups are encrypted (GPG) before being sent to storage. → Security

Access is role-based and limited to staff who need it, with quarterly access reviews, 3-day de-provisioning after termination, and background checks. → Security

We run regular vulnerability scans, annual penetration tests (Bugcrowd), and continuous log monitoring. → Security

For data processed through the apps, we act as a processor on your instructions.

For limited account/usage data (billing contacts, logs) we act as an independent controller.

→ GDPR policy, DPA

Mainly what's needed to run the apps and your account (name, email, usage data).

→ GDPR policy §5

We do not sell personal information.

→ DPA §2.5

We process personal data under GDPR, UK GDPR, and CCPA, and use EU/UK Standard Contractual Clauses for international transfers.

→ DPA

Primary processing takes place in the EU. Where data is transferred outside the EEA / UK / Switzerland, we apply Standard Contractual Clauses and appropriate safeguards.

→ DPA §6

Atlassian, Mailgun (default email), optionally Google/Microsoft/custom SMTP for email, Wasabi (backups), and OVH (hosting). → Subprocessors

Data tied to your organization is kept as long as it requires. On completion we return or delete it at your choice, unless longer retention is required by law.

→ GDPR policy

If we act as processor, please direct the request to your organization (the controller); we assist as needed. If we act as controller (e.g. for marketing), email contact@warsawdynamics.com.

→ Privacy Policy §12