Every release gets a green light —
or a reason it doesn't.
Sign-off gates for every release: who approved what, when, and what's still blocking — right inside Jira.
Release readiness is computed from real gate approvals, not a status someone typed in. Every decision is logged, permanently.
What Greenlight does
One gate board per release. No spreadsheets, no "reply-all to confirm QA signed off."
Gate board per release
QA, Security, Docs, Legal… each gate has an owner, live-linked Jira issues, checklists, and evidence links. Readiness is computed, never asserted: a release is ready when every required gate is approved.
An audit trail auditors accept
Every approval, rejection, revocation, and override is logged with actor, timestamp, and note. Export any release as a readiness report — a compliance snapshot — in one click.
Catches the drift
Issues that reopen after a gate was approved, Jira versions released while gates are red, targets at risk: surfaced in-app, never silently ignored. Optional Rovo agent answers "what's blocking 2.4?" in chat.
See it in Jira
A release's gate board and the Insights view — all inside your existing Jira project.
Built to stay out of your way
Runs on Atlassian
Egress-free by design — no external servers, no third-party services, no analytics beacons.
Your data, your site
Everything lives in Forge SQL inside your own Atlassian site. We never see it.
Works without Rovo
Fully functional on its own. The Rovo agent is an optional convenience layer over the same data.
Not on the Marketplace yet
Greenlight is finishing its Atlassian Marketplace review. Leave your email and we'll let you know the moment it's installable.