Inspiration

We run a small studio where AI agents do much of the work. In one day our scheduler marked sixteen hourly runs as "done". Every run had exited cleanly, and the day ended with nothing sold or delivered. The process finishing and the work being verified are different facts, and Jira's Done column cannot tell them apart. As more tickets get closed by agents, that gap gets wider.

What it does

Evidence Gate adds one rule to Jira: an issue cannot move to Done without evidence.

  • Workflow validator. Add "Evidence required" to any transition. Without evidence the transition is refused with a message that says what to attach.
  • Issue panel. Shows whether the issue is verified and lists its evidence. Anyone can add a test run, a delivered file, a review, a customer approval or a payment proof, with a link or a note.
  • Rovo agent. Ask "Which Done issues have no evidence?", "Show the evidence on EG-1" or "Attach a test run to EG-1". Writes go through Rovo's confirmation card.
  • MCP tools and a skill. The same three actions are declared as rovo:mcp tools, with a SKILL.md that tells external coding agents to record proof before they report a ticket as finished.

All four surfaces read and write the same record, an issue property, so nothing leaves Jira.

How we built it

Forge, Node 24 runtime: rovo:agent with three action modules, rovo:mcp, rovo:skill, jira:workflowValidator (function-based) and jira:issuePanel in UI Kit. Evidence is stored in the issue property evidence-gate through the Jira REST API. The validation logic is one small module with no Forge imports, shared by the backend and the panel and covered by unit tests. No external services and no egress.

Challenges

  • A missing issue property and "no evidence" both look like a 404, so the app checks the issue first.
  • The validator has no user session, so it reads as the app and fails closed: if evidence cannot be read, the gate stays shut and says why.
  • Keeping the agent honest. Its instructions forbid calling an issue verified unless the tool returned evidence, and the tools reject evidence that has neither a link nor a note describing what was checked.

What we tested (on a live Jira site)

  • Transition to Done without evidence: refused. After adding evidence in the panel: allowed.
  • The agent, asked across all projects, found the one Done issue that had no evidence. In an earlier run it recorded a review on an issue after confirmation and showed the evidence on another.
  • Not yet tested: calling the MCP tools from an external agent.

Limits

Evidence is a link or a note written by a person or an agent. The app records it; it does not check that the link is true.

What's next

Evidence rules per issue type (for example, bugs need a test run), a project report of unverified work, and links from evidence to builds and pull requests.

Links

This project was built with AI coding assistance (Claude Code). All issues in the demo are demo data.

Built With

Share this project:

Updates

Submission history