DeutschRequest early access

Deterministic release readiness

Ship with evidence, not assumptions.

ReleaseProof turns a defined Jira scope into a clear readiness decision, an explainable score, and an issue-level evidence matrix.

Request early accessSee how it works
  • Jira-native scope
  • Read-only permissions
  • No generative AI
  • Fail-closed analysis
Illustrative product view

Release 4.8.0

42 issues in verified scope
Jira
92/100

Readiness index

7 checks evaluated3 findings need review
PAY-142Checkout validationReady
PAY-151Retry handlingReview
PAY-166Payment API migrationReview

The release gap

A green board is not a release argument.

Status meetings and handcrafted checklists rarely prove that every in-scope issue has the signals your gate expects. ReleaseProof creates one explicit inspection surface.

01

Scope drifts

Teams discuss different issue populations without noticing.

02

Evidence hides

Missing criteria, versions, blockers, or approval markers surface late.

03

Scores obscure

A number without issue-level reasoning cannot support a serious gate.

  1. 01Check statuses
  2. 02Check versions
  3. 03Check subtasks
  4. 04Check blockers
  5. 05Check acceptance criteria
  6. 06Build report
  7. 07Repeat

ReleaseProof consolidates these checks into one deterministic release analysis.

From Jira to decision

A short path with visible boundaries.

  1. 1

    Define release scope

    Choose the explicit business boundary.

  2. 2

    Select expected version

    Set the version every in-scope issue should carry.

  3. 3

    Run analysis

    Evaluate the complete issue population deterministically.

  4. 4

    Review findings

    Trace every warning or failure to its affected issue.

  5. 5

    Export evidence

    Carry the current result into the gate review.

Explainable by construction

Seven checks. No model interpretation.

Each rule evaluates a defined Jira signal and produces a result that teams can reproduce and inspect.

Inspect all rules
  1. 01Acceptance criteria present
  2. 02Accepted workflow status
  3. 03No open subtasks
  4. 04No blocking issues
  5. 05Correct release version
  6. 06No blocker label
  7. 07Approval documented

Scope integrity

A wrong version field must not hide release work.

JQL_SCOPE separates business membership from the expected fixVersion. VERSION_ONLY remains available for simpler release definitions.

ReleaseProof separates “belongs to this release” from “has the correct version assigned”.

Business scopeDEMO-101 · DEMO-102 · DEMO-103
Expected version4.8.0
Observed issueDEMO-102 · fixVersion missing
Analysis resultScope remains 3 issuesDEMO-102 fails version check

Issue-level evidence

See exactly what changed the result.

The matrix connects each rule outcome to the issue that produced it. Full Jira descriptions and acceptance texts are not sent to the Custom UI result.

Read the evidence guide
Illustrative evidence matrix
IssueCriteriaStatusSubtasksBlockersVersionApprovalResult
PAY-142
PAY-151
PAY-166

Trust boundaries

Small permissions. Bounded data. Safe failure.

The Forge app reads the Jira signals required for analysis, stores app-owned configuration, and stops when a complete result cannot be established.

Read-only Jira

Uses read:jira-work. No Jira write scope is requested.

App-owned storage

Uses storage:app for project configuration controlled by the app.

Data minimization

Frontend results omit full description and acceptance text sources.

Fail closed

Unexpected pages or unmappable issues abort the whole analysis.

Review security details

Use cases

Release evidence for software with real operating constraints.

01

B2B SaaS

Keep frequent multi-team releases inspectable.

02

Industrial software

Trace readiness across complex, long-lived products.

03

Automotive software

Complement disciplined gates with bounded Jira evidence.

04

Financial technology

Support controlled software change reviews.

05

MedTech software

Strengthen issue-level release traceability.

Who it is for

One gate, clear responsibilities.

  • 01Engineering leadership
  • 02Release management
  • 03Quality assurance
  • 04Platform teams
  • 05Jira administrators

Operational change

Replace gate ceremony with a repeatable evidence loop.

Before ReleaseProof

  • Manual filters
  • Spreadsheet checklists
  • Release meetings
  • Missing evidence
  • Inconsistent gates

With ReleaseProof

  • Repeatable rules
  • Single evidence matrix
  • Consistent release checks
  • Documented findings
  • Clear release status

Current product posture

Specific where it matters. Honest where validation remains.

ReleaseProof is in early access. The workflow and trust boundaries are documented; customer outcomes, certifications, and commercial terms will only be published when independently supportable.

Read security modelExplore documentation

Put your next release gate on evidence.

Request early access and tell us how your team currently decides release readiness.

Request early accessRead the docs