Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up after Veronica: Meet Aura — an AI Sprint Health Dashboard living inside Confluence

shivain gupta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 3, 2026

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:

  • It's a Confluence macro that pulls live Jira sprint data and renders a visual sprint-health dashboard right on the page.📊 Completion, remaining work & velocity — real story-point and issue metrics
  • Blocker detection — from real issue links, labels, and status, not guesswork
  •  Team workload — who's carrying what, at a glance
  •  Deterministic risk flag — HEALTHY / AT RISK / CRITICAL, calculated from objective signals (not vibes)
  •  AI Sprint Analysis — powered by NVIDIA Nemotron, it explains why the sprint is at risk and what the team should focus on next

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? 👇

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events