Question 1

What does Approval Evidence record?

Accepted Answer

For the request type you configure in a project, it records each observed version of a request: its identifiers and selected fields such as summary and status, the complete answers in its attached Forms, and its native approval state with the approvers' Atlassian account IDs. A new snapshot is stored only when something changed.

Question 2

How does it show that a request changed after approval?

Accepted Answer

The issue panel shows "Inputs changed after approval" when the app observes protected inputs changing after sign-off, with the sequence of captured versions so you can see what changed and when the app observed it. The app never approves, reverts or edits anything. If your process requires a new approval, you run it in Jira.

Question 3

What does offline verification check?

Accepted Answer

Each snapshot is chained to the one before it with SHA-256 hashes. A project administrator exports a request's full history as one JSON file, and the bundled command-line verifier checks its hashes and chain links offline, so inconsistent edits to a stored or exported history are detectable. Verification checks internal consistency; it does not authenticate the source or prove that every change was captured.

Question 4

What happens when the app can't read part of a request?

Accepted Answer

The record says so. If Jira permissions or app access rules deny or fail a read, that source is labelled in the panel's per-source coverage and the request shows "Incomplete evidence". Incomplete evidence is never shown as verified.

Question 5

Does any of our data leave Atlassian?

Accepted Answer

Captured evidence does not. Approval Evidence is built on Atlassian Forge, with no external backend and no data egress, and what it captures is stored in Forge hosted storage for your installation. Exports you save and support email you choose to send us are separate from the app.

Question 6

Can the app change our requests?

Accepted Answer

No. Its Jira access is read-only. It never approves, declines, transitions or edits a request, so installing it changes nothing in your workflow.

Question 7

Is this an electronic signature or a legal record?

Accepted Answer

No. Approval Evidence is not an electronic signature, notarization or legal-immutability service. Its records are tamper-evident, not tamper-proof: inconsistent edits are detectable. Its timestamps record when the app observed a state, not the authoritative time of each individual decision. It supports your audit process; it does not make you compliant by itself.

Question 8

What does it need to run?

Accepted Answer

Jira Service Management Cloud with company-managed projects, native approvals and Forms. You configure one request type per project. Jira events trigger capture attempts, and a reconciliation job runs every five minutes to catch missed events.

Question 9

Can we delete a request's evidence?

Accepted Answer

Yes. A project administrator can delete a request's stored evidence from its panel after disabling capture for the project. Deleting evidence never changes the request, its Forms or its approvals in Jira. How the app handles Atlassian account privacy is set out in the Approval Evidence privacy policy.

Question 10

When can we install it?

Accepted Answer

Approval Evidence is coming soon to the Atlassian Marketplace. Leave your email on this page and we will send one message when it is listed, or write to hello@app-sync.com with your questions.