Inspiration

New Jira issues land with no context: nobody knows how urgent they are, who should own them, or whether the same bug was already reported. Triage Copilot answers all three questions at once, inside Rovo Chat.

What it does

Triage Copilot is a Forge app with a Rovo agent and an MCP server that share the same four read-only tools:

  • triage-issue — scores a Jira issue 0–100, assigns a priority band, suggests an assignee, lists reasons
  • find-related-issues — finds open issues related by keyword overlap (JQL text search)
  • search-confluence-docs — finds related Confluence pages (runbooks, incident notes, design docs)
  • find-owner — suggests an owner: project lead, assignees of related issues, enriched with Teamwork Graph teams

Live demo result (demo site, verified 2026-11-17): issue CLSD-6 "Login page crashes on mobile Safari" triaged as Priority Highest, score 95, suggested assignee Alana Grant (project lead), related issues CLSD-7 and CLSD-8 found, and the "Login outage runbook" Confluence page surfaced first.

How we built it

Forge (Rovo agent + MCP server) with a pure, deterministic scoring engine in JavaScript (fully unit-tested, 10/10 tests), Jira REST + Confluence CQL via Forge asUser, and Teamwork Graph persisted queries for team lookup. The demo video is a 45-second screen recording of the working agent.

Challenges we ran into

  • Forge passes action inputs top-level on the first argument, not under req.payload — every action initially failed with "issueKey is required".
  • Confluence search lives at /wiki/rest/api/content/search, not /wiki/rest/api/search.
  • Forge's route already URL-encodes interpolations, so our own encodeURIComponent double-encoded the CQL query.
  • Rovo does not exist on a free Atlassian dev site — testing needed a 90-day Forge demo site.

Accomplishments that we're proud of

End-to-end live triage on a real Jira + Confluence demo site: correct priority, correct owner, related issues and the right runbook in one answer — with a deterministic, testable scoring engine behind it.

What we learned

Read-only tools keep the blast radius small; deterministic scoring makes an AI agent's answers testable; and the Forge platform's small API quirks (payload shape, encoding, endpoints) are where the real debugging time goes.

What's next for Triage Copilot

  • Workload-aware assignee ranking (one batched JQL count per candidate set)
  • An "Apply triage" write action that sets priority/assignee
  • A Jira issue panel showing the triage inline in the issue view

Try it

Built With

Share this project:

Updates

Submission history