Signoff: Provable Approval Workflow for Jira

Approvals in Jira usually end up as a checkbox, and a checkbox proves nothing. Six months later the auditor asks not who approved the issue, but what exactly was approved, and the issue has changed twelve times since. Signoff puts a validator on the transition: until the required signatures are collected, the transition does not happen. Every signature is stored with a fingerprint of the fields it was given for, so editing one of them makes the approval stale, the transition closes again, and the panel shows the change side by side. Rules are set per transition: who approves, in how many steps, by user, group or project role. A rejection outweighs any number of approvals and requires a reason. The issue panel shows what is missing, a waiting-for-me list floats the longest wait to the top, and a CSV export gives the auditor decisions and transition attempts interleaved in time order. The app has no outbound network access at all.