Fresh off shipping Veronica, I'm kicking off my next Forge build this week — and I'm genuinely excited about this one.
The problem: Sprint health lives in Jira, but the people who need the summary — leads, stakeholders, cross-functional partners — live in Confluence. So they either dig through Jira boards or wait for someone to hand-write a status update. That gap is where sprints quietly go off the rails.
Aura closes that gap. 🎯
It's a Confluence macro that pulls live Jira sprint data and renders a visual sprint-health dashboard right on the page.Drop the macro in, pick a project and sprint, and you instantly see:
The part I care most about: the AI explains, it doesn't decide. The risk status is computed deterministically, and the model only summarizes the "why" and recommends focus areas. No hallucinated health scores.
The stack, for the curious: Confluence Macro → Forge Resolver → Jira REST + Agile APIs → deterministic sprint analytics → NVIDIA NIM → AI summary. All on Atlassian Forge (UI Kit), with the API key kept strictly backend-only and egress locked to a single endpoint. Auto-refreshes every 5 minutes so the dashboard is always current.
This is a proper Confluence + Jira cross-product integration — the kind of "your tools should talk to each other" experience I love building on Forge.
Building it this week. Will share progress, learnings, and the honest engineering trade-offs (looking at you, sprint burndown historical data 👀) as I go.
Would love to hear: what's the one sprint signal you wish your team could see without opening Jira? 👇