Inspiration
Release leads need to know which dependency to clear first. Jira shows links issue by issue, so the release lead has to piece together which blocker affects the most work.
What it does
Release Relay ranks open blockers by the number of distinct work items they affect in a selected Jira release. Each card lists the work items waiting on that blocker and flags dependencies across Jira projects. If Jira cannot verify a linked item’s status, the report marks it for verification and shows any scan limits.
How we built it
Release Relay is a Jira project page built with Atlassian Forge Custom UI. Forge Bridge reads release versions and issue links with the read:jira-work scope. The report uses Jira results visible to the signed-in user and calculates the ranking in memory.
What we tested
On a Jira Cloud test site, two open work items in an unreleased version shared one blocker. The report showed 2 checked, 2 affected, 1 blocker. After the blocker moved to Done and the report was refreshed, the same release showed 2 checked, 0 affected, 0 blockers. Eight automated checks and Forge lint passed. Forge version 2.0.0 was deployed to production.
AI assistance
The entrant initiated Release Relay, set up the Atlassian developer account and Developer Space, and reports doing most of the work on the idea and code in collaboration with OpenAI Codex. Codex proposed the initial concept and generated application code, the user interface, synthetic Jira test data, automated tests, and draft submission materials. The entrant authorized testing on the Jira demo site.
