Inspiration
Every new Jira issue is a small job in itself: someone has to read it, decide what kind of work it is, judge how urgent it is, find the right person, and write the first reply to the reporter. On a busy team that triage queue is where issues go to wait. TriageGenie does the whole first pass the moment an issue is created — and shows its working, so a human can trust it, check it, or overrule it in one click.
What it does
Auto-triage on creation: a Forge trigger fires on every new issue and applies labels, sets the priority, and posts a drafted first response as a comment — verified live in about 11 seconds. Classification into 7 categories — incident, security, bug, feature, task, question, docs — with security and incident keywords always winning. Priority score 0–100 with reasons: every point is listed in the panel, so the score is explainable, not a black box. Suggested labels (triagegenie, category:task, plus crash, security, billing, and more from keyword rules). Suggested assignee: skill match against the issue text and components, minus current workload, plus an on-call bonus for incidents. It never suggests someone already at capacity — and it says so when nobody matches. Draft first response + fix plan: a reply to the reporter and category-specific next steps. Issue panel: open any issue and the TriageGenie panel shows the full triage; one click on Apply writes labels, priority, assignee and the first response to the issue — and it never posts the same comment twice. Grounded in Teamwork Graph: similar past issues, recent commenters, linked goals and linked docs are read through curated GraphQL queries. Rovo agent + MCP: the same four actions (triage an issue, find similar issues, suggest an assignee, draft a response) are a Rovo agent and an MCP server.
How I built it
A Forge app (TypeScript + React + UI Kit 2). The modules are jira:issuePanel for the panel, a trigger on avi:jira:created:issue for auto-triage, rovo:agent with four actions, and rovo:mcp exposing the same actions as MCP tools. All triage decisions live in src/triage.ts — pure, deterministic functions with no API calls, covered by 84 offline tests against mock data. The Forge handlers only fetch data (Jira REST + Teamwork Graph via src/twg.ts) and write results back. One subtlety: a trigger invocation has no user context, so Jira calls on the trigger path use api.asApp(), while the panel and Rovo actions keep api.asUser().
Challenges
The trigger "never fired": it did fire — and died with a 401. A trigger has no user, so api.asUser() has no auth type available. The fix was to use api.asApp() on the trigger path. The panel refused to render: Forge UI Kit 2 rejects native HTML, and the panel used native HTML bold tags in six places. Replaced with the @forge/react Strong component. Apply posted the first response twice: Apply now reads the issue's existing comments first and skips the post when the first response is already there.
Accomplishments
Verified live end to end on a real Jira Free site: a fresh issue is auto-triaged in ~11 seconds (labels + one bot comment), the panel renders with the full score breakdown, and Apply lands the changes without ever double-posting. 84 unit tests and 56 manifest checks pass; forge lint is clean. The judges' install link is live (Sharing with anyone, Jira only).
Honest note on Rovo
The Rovo agent (rovo:agent + four actions) and the MCP server are part of the app, but the demo site is Jira Free, which has no Rovo — so the video demonstrates the trigger and the panel, which are what a Free site can show. Judges installing on a site with Rovo can try the agent there. Nothing in the video is faked: every frame is the real app on the live site.
What's next
Show the Rovo agent live on a site that has Rovo. Richer fix plans generated from the similar-issues context. Confluence linked-docs context via a native Teamwork Graph query.
Testing instructions (for judges)
- Install from the installation link (Jira only, free): https://developer.atlassian.com/console/install/822e6b7d-3afe-401b-a26a-2ed420fef57d?signature=AYABeFp2w1i8742Dg16oqcjli4oAAAADAAdhd3Mta21zAEthcm46YXdzOmttczp1cy13ZXN0LTI6NzA5NTg3ODM1MjQzOmtleS83MDVlZDY3MC1mNTdjLTQxYjUtOWY5Yi1lM2YyZGNjMTQ2ZTcAuAECAQB4CxqLTo9l4lqXuFjNim1xJM%2Bp%2F3TVP9xHS2BrU5DRRucBIH4RMori4nvs08M1H7SrwgAAAH4wfAYJKoZIhvcNAQcGoG8wbQIBADBoBgkqhkiG9w0BBwEwHgYJYIZIAWUDBAEuMBEEDFX%2BDkZXzUpLdLDLtgIBEIA713KxxAbFuwkC%2FKDO8c2s28iWuhpn17IT0wlWYyU4cF2%2Bkx%2Bp5V1%2BKfMN%2F02uGwarBBnNtwNywIUYkAsAB2F3cy1rbXMAS2Fybjphd3M6a21zOmV1LXdlc3QtMTo3MDk1ODc4MzUyNDM6a2V5LzQ2MzBjZTZiLTAwYzMtNGRlMi04NzdiLTYyN2UyMDYwZTVjYwC4AQICAHi9bVMAkme4qVQX1fQHo6ePw3H40A7cGfz7yrmSfBWMXgFor7BWxXNFL262ypxeG%2BCFAAAAfjB8BgkqhkiG9w0BBwagbzBtAgEAMGgGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQMIaJBEQIzTNLzFblRAgEQgDtF8IBUPq2iqKYae7KmOSXVuq3uMxvOnsJ1rM8PYK8M4MoH1Gs7BLxGKQb27xLQ%2BkQ%2FWADOX10iqk0YxwAHYXdzLWttcwBLYXJuOmF3czprbXM6dXMtZWFzdC0xOjcwOTU4NzgzNTI0MzprZXkvNmMxMjBiYTAtNGNkNS00OTg1LWI4MmUtNDBhMDQ5NTJjYzU3ALgBAgIAeDYASx0XCjkny4iLV6vz%2BKtEGSGT6kdt0QRpkn6D%2FlVEAWYUBBAKzH45dwrOQSP1Mk8AAAB%2BMHwGCSqGSIb3DQEHBqBvMG0CAQAwaAYJKoZIhvcNAQcBMB4GCWCGSAFlAwQBLjARBAwfsbx7eIFigPH0hIECARCAO0vjk72gc%2FuPt47qW9h%2Bs6g%2F8AOm28wy3mYM4uhfcjpfeFfgfE%2Brz4VV5yU3OaxX7Em4d4jiv75MLyTqAgAAAAAMAAAQAAAAAAAAAAAAAAAAAG5kALIhly0MMr5h%2Fa1BkNj%2F%2F%2F%2F%2FAAAAAQAAAAAAAAAAAAAAAQAAADI4uaixK28ISSkwr%2B3xfvQ7KCVvRdda91fR40gUqnvAhcAiZeN7VUFC%2BfTcRiA8%2ByydgMXVhTJNcp5%2BzXYCWGwG%2Ba4%3D&product=jira 2. Create a new issue in any project — within a minute it gets labels (triagegenie, category:task), a priority, and a first-response comment. 3. Open the issue → TriageGenie panel (issue menu → View app actions) → see the score breakdown, suggested labels, assignee note, draft reply and fix plan → click Apply triage. 4. No login beyond your own Atlassian site is needed; the app needs no configuration.
Built With
- atlassian-mcp
- forge
- jira
- react
- rovo
- teamwork-graph
- typescript
- ui-kit-2