Skip to main content

Signed Approvals for Jira

Replace ad-hoc Jira approvals with cryptographically-signed, dual-signature approval workflows — for change management, ops, engineering leads, and finance approvals.

🚧 In development. Signed Approvals is the third app in the Attestsys suite, planned for release after Evidence Pack. Premium-tier feature on the Marketplace.

The problem​

"Approved" in a Jira comment is not evidence. It's not signed. It's not bound to a specific request. It's not even necessarily from the person whose name appears next to it.

For real change-management controls — production deploys, contract approvals, payment authorisations, engineering-change records — auditors and regulators want a signed approval that can be independently verified to have come from the named approver at the named time on the named change.

How it works​

  1. The requester opens a Jira issue and triggers an approval request from the issue panel.
  2. The requester signs the request with their bound identity (per-tenant ECDSA key, or a wallet via EIP-191 for organisations that already manage identity through wallets).
  3. The named approver receives the request, reviews the diff/payload, and countersigns.
  4. Both signatures, the original payload, the requester→approver linkage, and an RFC 3161 timestamp are folded into a hash-chain entry on the Audit Log.
  5. The signed-approval record exports into the same verify.html-compatible bundle as every other Audit Log evidence pack.

Templates​

Built-in approval templates cover the most common change-management workflows:

  • Production deploy — bind to the Jira issue, the linked GitHub release, and the deployer's signed acknowledgement.
  • Engineering change — capture the change description, blast-radius assessment, and reviewer countersignatures.
  • Security review — link the review to the asset, the reviewer, and the verdict.
  • Contract approval — escalates to contract-level escrow signing for organisations that need it.

Stay in the loop​

Signed Approvals will be available to Audit Log Premium customers when released. Install the Audit Log first; the in-product upgrade prompt will appear when Signed Approvals ships.