What ReleaseProof does, what it accesses, and what remains a human responsibility.
What is ReleaseProof?
ReleaseProof is Jira-native release-readiness software that turns a defined issue scope into deterministic rule results, findings, a score, and an evidence matrix.
How does ReleaseProof work?
A team configures its supported Jira signals and release scope, runs a complete analysis, reviews exceptions by issue, and reruns after correcting source records.
What is release readiness?
Release readiness is the current evidence that a defined release population meets a team's explicit gate rules. It supports, but does not replace, the human release decision.
How does ReleaseProof define release scope?
VERSION_ONLY uses Jira version assignment. JQL_SCOPE defines a business population independently and checks the expected version as a separate rule.
Why isn't fixVersion enough?
If fixVersion alone defines scope, a missing or wrong value can remove an issue before it is checked. JQL_SCOPE keeps that issue visible and reports the version failure.
What Jira permissions does ReleaseProof need?
The current Forge app declares read:jira-work for required Jira signals and storage:app for app-owned configuration. It does not request Jira write scopes.
Can ReleaseProof support audit processes?
It can support internal control and audit workflows with repeatable, issue-level release evidence. It does not certify compliance or replace qualified review.
Where does ReleaseProof run?
Release analysis runs in the Jira-native Atlassian Forge app. The Vercel-hosted public website is separate and does not process Jira release-analysis data.
Does ReleaseProof approve releases?
No. It provides deterministic readiness evidence. Accountable people make the release decision in their established process.
Does it use generative AI?
No. The readiness analysis uses explicit code-based rules and does not call a generative AI model.
Does it change Jira data?
No. The current app requests Jira read access and app storage for its configuration. Findings are corrected by authorized users in Jira.
Continue exploring
Product overview