Every incident starts the same way: someone pages a human, the human reads five tabs, and twenty minutes disappear before anyone knows what broke. Incident Triage Copilot ends that. The moment a Jira or JSM issue is created, a Forge trigger drafts a triage: what broke, the likely cause (quoted from the most similar past incident), blast radius, a suggested priority, and the person most likely to fix it — ranked from the Teamwork Graph by who last touched the service and who resolved similar incidents. The draft lands in an issue panel with its confidence score and its evidence. A human approves, edits, or ignores it. Nothing is ever assigned or changed silently. The same engine is a Rovo agent ("Triage the newest incident") and an MCP server with read-only tools, so any MCP client can ask the same questions. The triage engine is deterministic and runs entirely inside Forge — no external server, no API keys, no secrets. The Teamwork Graph queries are persisted Cypher, and when the graph has no answer the app falls back to Jira history instead of failing.

Built With

Share this project:

Updates

Submission history