Product

One release gate. Seven explicit checks.

Define the release scope in Jira, run a deterministic analysis, and inspect every result down to the affected issue.

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

Operating model

Configuration, analysis, evidence, decision.

  1. 01

    Configure

    Select a supported acceptance-criteria source, choose VERSION_ONLY or JQL_SCOPE, and set the expected version.

  2. 02

    Analyze

    Collect the complete Jira population and evaluate seven deterministic rules.

  3. 03

    Inspect

    Move from readiness summary to the issue-level evidence matrix.

  4. 04

    Act

    Correct source issues in Jira, then run a fresh analysis.

Product surface

Every step needed for an inspectable release gate.

01

Release analysis

Runs the complete deterministic evaluation on demand.

02

Release scope

Defines the Jira issue population independently of rule outcomes.

03

Deterministic rules

Evaluates seven named conditions without model interpretation.

04

Evidence matrix

Maps every rule result to an in-scope Jira issue.

05

Issue findings

Surfaces the exact exceptions that need review.

06

Release score

Summarizes current results without replacing issue-level evidence.

07

Report

Presents the current analysis for the human gate review.

08

Project configuration

Stores supported field, status, marker, and scope choices.

Result design

Useful for a gate. Deliberately not a Jira replica.

The public result is minimized to what the Custom UI needs for readiness, display, and traceability. Detailed source content stays in Jira.

Included in the UI result

  • Overall readiness index
  • Rule outcomes
  • Affected issue key and summary
  • Evidence detail state
  • Report view

Kept outside the UI result

  • Full Jira descriptions
  • Full acceptance-criteria text
  • Unneeded labels and relationship objects
  • Generative interpretation

Evidence matrix

Every exception has an address.

Use the matrix to find the exact issue and rule intersection that needs review.

Understand the matrix
Illustrative evidence matrix
IssueCriteriaStatusSubtasksBlockersVersionApprovalResult
PAY-142
PAY-151
PAY-166

Architecture

A visible chain from source to human review.

A bounded analysis path
  1. Jira scopeRead required issue signals through Forge
  2. Deterministic rulesEvaluate seven explicit conditions
  3. Minimized resultReturn score, findings, and display data
  4. Human gateReview evidence and make the decision

Put your next release gate on evidence.

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