Greenlight

Documentation

Release notes

What's live on the Atlassian Marketplace right now. One entry per production version — installed sites upgrade automatically, and every version keeps Greenlight's zero-egress posture: no data ever leaves your Atlassian site.

2.5.0 — plan groundwork

August 7, 2026

Groundwork for the plans Greenlight will offer from its next major release.

The release-readiness workflow is unchanged: releases, gates, checklists and linked issues, sign-off and revocation, the full audit trail with evidence snapshots, templates, the readiness report, nudges, comments, My gates, the release countdown, the timeline, the Rovo agent and the Jira Automation action all work exactly as before.

A set of organization-scale capabilities — approver quorums, conditional gates, gate escalation SLAs, locked template gates, PDF and CSV export of the readiness report, the portfolio reporting gadgets, and the admin usage panel — now belong to a higher plan arriving with that release, and are not part of the app today.

No new permissions and no database changes. Still zero egress — Runs on Atlassian.

2.4.0 — the gate board

August 5, 2026

A focused release about seeing the whole release at once. Installed sites upgrade automatically; no new permissions are requested, and Greenlight still runs with zero egress (Runs on Atlassian).

Every gate at a glance

  • The gate board — a rail lists every gate in your release with its status, owner and item progress, while the pane beside it holds the one you're working on. Previously each gate was a card you expanded in turn, which meant reading the whole page to learn who you were waiting on — and losing that overview the moment you opened one. The board opens on the gate that most needs a human, and a gate you select yourself survives a reload.
  • "Waiting on" — the readiness bar tells you how much is done; this new line tells you who is holding the release up, worst first, or that the release is ready.
  • Reordering and "Add gate" now live in the rail, next to the list they act on.
  • Narrow windows and the Jira issue panel keep the familiar stacked layout.

Pages that start at the top

  • No more repeated heading — the project, global and admin pages no longer sit below a heading Jira already shows above them, so content starts at the top of the page instead of halfway down.
  • Greenlight's own icon in Jira's navigation, in place of the generic default.

Under the hood

  • Schema self-heal — if a database table or column is ever missing, the app now applies pending updates and retries once, rather than showing an error until the next hourly sweep. Invisible when nothing is wrong.

2.3.0 — panels, SLAs, gadgets & a stronger audit trail

July 31, 2026

One big update — everything built since launch. Installed sites upgrade automatically; no new permissions are requested, and Greenlight still runs with zero egress (Runs on Atlassian).

Gates grow up

  • Approver panels (quorum gates) — a gate can require M of N named approvers (e.g. 2 of 3 security reviewers) instead of a single owner. Each panelist approves or rejects individually; the gate's sign-off is the rollup, and the report lists every approver with their timestamp and note.
  • Conditional gates — a template gate can declare when it is required: release type in a set, and/or linked work touching given components or labels. It always seeds (as optional) and flips automatically as issues are linked; every flip is audit-logged, and a human editing Required detaches the condition. Marked ⚡ on the gate card.
  • Escalation / SLA — "if unapproved N days before target, escalate": the daily sweep notifies an optional backup approver and the release managers, once, in-app; escalations appear in the report under Exceptions & overrides.
  • Comments & @mentions — a lightweight thread on every gate. Type @ to mention someone; recent mentions of you surface in the hub attention strip.
  • Gate reordering — move gates up/down on the release page.

See your work, everywhere

  • "My gates" + dashboard gadget — a personal, worst-first queue of every gate you own or sit on a panel for, across all projects you can see. As a Jira dashboard gadget and a tab on the global overview.
  • Release timeline — the global overview gains a cross-project Timeline view: one bar per release from creation to target date, colored by status, with a today line and click-through.
  • Weekly digest — a Monday hub card (and a Rovo action: "What needs attention this week?") listing the releases that need attention, why, and the outstanding gates grouped by owner. Computed live, nothing stored.

A reporting pack for the dashboard

Seven new gadgets alongside My gates — add them from any Jira dashboard's gadget directory: Release radar, Release countdown, Risk insights, Bottleneck teams, Release velocity, Override watch, and Stale gates. All respect project permissions and are read-only over existing data — see the documentation for what each one shows.

A stronger compliance artifact

  • Evidence snapshots — every approval, rejection, and release-override now freezes the gate's checklist and evidence links into the audit event itself. The report gains an "Evidence at sign-off" section; the record stays defensible even if a linked page is later edited or deleted.
  • True PDF & CSV export — the readiness report downloads as a real PDF (generated in your browser — no egress) and as a CSV of the sign-off table, alongside the existing markdown.

Governance for admins

  • Template versioning — templates version on every edit; each release records which template and version seeded it.
  • Locked gates — a Jira admin can 🔒-lock required gates on global templates; project teams can't delete them or make them optional on seeded releases. The lock survives "save as template".
  • Private usage analytics — a Usage section on the admin page: active users, actions, and views by surface over 7/30/90 days, counted entirely in your site's Forge SQL. Counts only — no names, nothing leaves Atlassian.

Automation & polish

  • Jira Automation action — "Create Greenlight release": pick a template, name the release from smart values, and let your rule seed the gate board. Pair it with Jira-native triggers like "version released".
  • Bulk operations on the hub: archive/unarchive several releases, or shift target dates by ±N days.
  • Full dark mode — every surface now follows your Jira theme.
  • A tighter layout — the project page no longer repeats the heading Jira already shows above it, so releases start at the top of the page instead of halfway down. On a release, each gate's "add item" form stays out of the way until you ask for it, and an approved gate no longer wears three badges that all say the same thing.

2.2.0 — first public release

July 12, 2026

Initial public release of Greenlight — Release Readiness & Approvals for Jira.

  • Gate board per release — owners, team labels, checklists, evidence links, and live-linked Jira issues. Readiness is computed, never asserted: a release is ready when every required gate is approved.
  • Sign-offs with a permanent audit trail — approve, reject, revoke, reopen, and release-manager overrides, each logged with actor, timestamp, and note.
  • One-click readiness report — a compliance snapshot you can copy, download as Markdown, or print.
  • Cross-project overview, in-app attention feed, and insights: cycle time, sign-off lead time, and approval bottlenecks.
  • Jira version lifecycle sync — linked fixVersions update the release automatically; drift after approval is surfaced, never hidden.
  • Release notes drafting and a seeded sample release for easy onboarding.
  • Optional Rovo agent — ask "what is blocking 2.4?" in chat; the app is fully functional without it.
  • No data leaves Atlassian — Forge SQL storage only, no egress (Runs on Atlassian).