Skip to main content
{ Reporting and Compliance / Task Management }

Jira Agent Ticket Report

Reports on the open Jira tickets that Ghost Agent Factory agents filed, by type, age, and status, and on what changed in them during the last sprint.

What this agent does

This read-only agent reports on the Jira tickets that Ghost Agent Factory agents created. It breaks the open tickets down by the agent that filed them, the kind of finding, severity, age, and status. It summarizes what happened during the last sprint: tickets opened, fixed, closed by the agent, closed by a person, and reopened. It lists the tickets nobody has updated within a set window.

The challenge

Once agents file tickets automatically, nobody has a clear view of the whole queue. It is hard to tell which agents produce work that gets done, which ones produce tickets people close without acting, and which tickets nobody has touched for months. Sprint reviews cover the team's planned work, and nobody reviews the tickets agents filed.

The solution

The agent reads every ticket the Ghost Agent Factory workflows filed and groups them the way a team lead would look at them. It compares the last sprint with the ones before it, so the team sees trends without building a dashboard. It flags stale tickets and agents whose tickets people mostly close unfixed. Provides one report per sprint on how the agent-filed work is moving.

Workflow

  1. 01

    Find agent tickets

    Find the tickets Ghost Agent Factory workflows filed, using the labels the ticketing agents apply.

  2. 02

    Break down the open queue

    Group open tickets by the agent that filed them, finding type, severity, age, and status.

  3. 03

    Summarize the sprint

    Count the tickets opened, fixed, closed by an agent, closed by a person, and reopened during the last sprint.

  4. 04

    Report

    Publish the breakdown, the sprint summary, the trend against earlier sprints, and the stale tickets.

Agent template 

# Jira Agent Ticket Report

## Measurable outcomes

At the end of every sprint, the team knows how many agent-filed tickets are open, how old they are, and what moved during the sprint. Track open tickets and the tickets opened, fixed, and closed per sprint.

## Procedure

Run at the end of each sprint in the Jira projects I set. Find the tickets Ghost Agent Factory workflows filed by the labels the ticketing agents apply, and ignore every other ticket. Group the open tickets by the agent that filed them, the kind of finding, severity, and status. Break them into age bands of under a week, one to four weeks, one to three months, and over three months. For the last sprint, count the tickets opened, the tickets fixed and closed, the tickets an agent closed because the finding went away, the tickets a person closed or rejected without a fix, and the tickets reopened. Compare those counts with the previous three sprints. List the tickets with no update in the last 30 days, oldest first, unless I set another window. Call out any agent whose tickets people mostly close without a fix, since its findings may need tuning. Report a count it could not read as not available, never as zero.

## Requirements

It needs read-only Jira API access to the projects in scope, including issue history and sprints, and nothing more. It never creates, edits, or closes tickets.