Atlassian Forge · Jira Cloud
Release Readiness Gate
The problem
A team's pre-release checklist lived in a Confluence page. It was followed when
people remembered, and the only evidence a check had happened was that somebody
said so in standup. Jira's built-in workflow validators couldn't express the rules
— things like "at least two different people approved, and the assignee
isn't one of them".
What I built
A Forge app with a configurable rules engine. A scorecard on every issue shows
which checks pass and why, and every gated transition posts a structured audit
comment. Project admins configure the rules themselves in a settings screen —
nine rule types covering field content, regex formats, labels, issue links,
blockers, due dates and multi-person approvals.
Since Jira's own validators couldn't express those rules, the app ships one. The
gate runs inside Jira's workflow engine, so it holds on the status
dropdown, a card dragged across a board, a bulk change, an Automation rule and
the REST API — not only on the button in the app's own panel. Admins attach it to
the transitions that matter in the workflow editor, because Jira already owns
transition configuration and a second picker inside the app would only drift out
of step with it.
The decision that shaped it
Every rule evaluation lives in a pure module that imports nothing from the Forge
platform. It takes plain objects and returns plain objects, so the whole rules
engine is unit tested in seconds with no Jira instance and no mocks. The adapters
around it stay thin enough to review by eye — and the scorecard, the workflow
gate, the change trigger and the nightly sweep are four callers of one function,
so what the panel shows and what Jira enforces cannot drift apart.
Code and case study on GitHub → — Release Readiness Gate