The problem

Every software team drowns in the same first hour of an issue's life. A bug report lands with no priority, the wrong type, no labels, no owner — and sits there while someone eventually reads it, guesses at its urgency, hunts for duplicates, and figures out whose problem it is. Multiply that by every issue, every day: triage is the invisible tax on every team's throughput, and doing it badly means production incidents wait in the same queue as typos.

What TriagePilot does

TriagePilot is a Forge app for Jira Cloud with two faces sharing one brain:

1. A Rovo agent for chat. Ask TriagePilot to triage an issue and it:

  • reads the issue in full — summary, description, status, and the recent comment thread — through its fetch-issue-context action;
  • classifies the issue type (Bug / Story / Task / Incident) from the actual language of the report;
  • scores priority from concrete impact signals (production, customers affected, data loss, security, blocked work) — and can show its reasons;
  • searches the project for similar issues with find-similar-issues, flagging likely duplicates before they waste a second investigation;
  • suggests labels and ranks candidate assignees with suggest-assignees, weighting who resolved similar issues before;
  • drafts a first response (for support-style issues) or a fix plan (for engineering issues).

Then — and only after the user explicitly confirms — it writes the decision back with the apply-triage action: labels, priority, assignee, and the drafted comment.

2. A Jira issue panel for the issue view. The same verdict, rendered natively on the issue: suggested type and priority with their evidence, proposed labels, a duplicate warning when a near-identical issue exists, the best assignee with the reason — and a one-click Apply this triage button.

Why it is built this way

  • Deterministic core, LLM narration. The classification, priority scoring, duplicate detection, and assignee ranking live in a pure, unit-tested heuristics module. The agent reasons and writes on top of those facts instead of hallucinating them — and the panel shows the identical verdict without an LLM round-trip, so it's instant.
  • Human-gated writes. TriagePilot never silently changes an issue. The single write action is only invoked after an explicit confirmation, and only with the fields the user confirmed. In the panel, applying takes a deliberate click.
  • Permission-respecting. Everything runs asUser() through @forge/api: the agent sees and changes only what the person using it is allowed to see and change. Three scopes total, no external services, no stored data, no API keys.

How it is built

  • Atlassian Forge (Node 22 runtime): one rovo:agent, four action modules (three GET, one UPDATE), one jira:issuePanel.
  • UI Kit (@forge/react) for the panel; @forge/resolver + @forge/bridge connect it to the same handlers the agent uses.
  • Jira REST API v3 via @forge/api, including the current /rest/api/3/search/jql endpoint; ADF ⇄ text conversion is hand-rolled and unit-tested.
  • The agent's prompt lives in its own resource file, keeping the manifest lean; action descriptions are written as the questions they answer, which is how Rovo picks between them.

Try it

Installation link: https://developer.atlassian.com/console/install/bcd4929c-370a-4fe5-a9b1-a0a2f286f0fa?signature=AYABeGzMHR2Qg5WQpBq3cP0a6GgTjD9B4bQ9WgS8Pz-5bS4U2bL4mXqM8lL7eY_7Z8v2gYv0V1iZ0b1Q7K_9o8o5eC_1r5p8p9q4Gk3V9h9W5eN4yM8Q&product=jira

  1. Install TriagePilot on a Jira Cloud site with Rovo enabled (Standard/Premium/Enterprise or trial).
  2. Create a few untriaged issues — a vague bug report, a production incident, a feature request.
  3. Open one and scroll to the TriagePilot panel in the issue view to see the verdict; click Apply this triage.
  4. Open Rovo chat, pick TriagePilot, and say "Triage issue PROJ-123". Ask it to draft a first response, then confirm applying the triage.

Demo video: https://youtu.be/m1afK11TuvI

What's next

A reusable rovo:skill triage playbook for other agents, Teamwork Graph enrichment for assignee ranking (team membership + current load), an rovo:mcp surface for external MCP clients, and an automation recipe that pre-triages new issues while keeping every write human-confirmed.

Built With

Share this project:

Updates

Submission history