The work board

One row per ticket: its status, the pull requests on it, the agent working on it, the evidence to look at — and the column the board exists for, what is waiting on you. Code → Work board.

Tickets lead

The board starts from your tickets, not your checkouts. A ticket sitting in To Do with nobody on it is exactly the one you need to see, and it has no branch anywhere — so nothing has to be registered in AIOAT for the board to be useful.

Tickets come from Jira, using the site, email and API token on your active profile (Profiles → Jira). ⚙ Query decides which ones; the default is everything assigned to you that isn't done:

assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC

Any JQL works — project = NBC AND sprint in openSprints(), a filter you already use, a team's board. The query is remembered per machine.

No Jira on the profile? The board still shows the branches and agents AIOAT knows about, and tells you what to add to get the rest.

Pull requests, found by ticket key

AIOAT searches GitHub for pull requests mentioning the ticket key, across every repository you can see — no clone, no registration. For each one it then reads the detail: checks, review decision, who was asked to review and who actually reviewed, the size, and the screenshots, GIFs and videos in the description and comments.

Because one ticket often spans several repositories, they all land on the same row: the API change, the client change and the docs change side by side, which is the thing a per-repository view can never show.

Scope the search. Unscoped, a search for NBC-1036 would reach all of GitHub and could surface a stranger's pull request that happens to mention the same key. With no owners configured AIOAT scopes it to work you are involved in; put your org in GitHub owners next to the query so a teammate's pull request on your ticket shows up too. Needs gh, signed in as the profile's GitHub identity.

What your agents are doing about it

This is the part no API can tell you. A session whose branch or title carries the ticket key is shown on that row with its state — working, waiting for you, idle — and the button opens its terminal.

An agent stopped mid-task is the first thing the board reports: it isn't working, and only you can unblock it. A ticket in To Do with an agent on it is not "not started", so it doesn't say so.

Reading a row

Column	What it holds
Ticket	Key (opens Jira), the workflow step as your project names it, the title, the assignee.
Agent	The AIOAT sessions on it and what they're doing; the local branch and how far it has drifted from its base.
Pull requests	One line each: `owner/repo #123`, size, checks, review, reviewers. Click to open it in an AIOAT browser window.
Evidence	🎞 media attached to the ticket · 📷 screenshots and videos in the pull requests · 📎 captures your own agents took · whether AIOAT's test run passed · 💬 comment count.
Waiting on	Computed, never typed. See below.

What "waiting on" means

Each pill is a specific thing someone has to do:

an agent is waiting for you — a session stopped on a question.
not started — a ticket to do, with no agent, no branch and no pull request.
in progress, but nothing is running — the ticket says work is happening; nothing here is.
ticket closed, pull request still open — the two disagree.
still a draft · checks failing · changes requested · nobody asked to review — per pull request.
commits, no pull request · behind its base · tests failing — from the local branch, when the repo is registered.

Merged work waits on nobody, however red its checks once were. Checks still running are not something a human can act on, so they raise nothing either — otherwise "needs action" becomes noise and you stop reading it.

Filters

Search covers ticket keys, titles, statuses, assignees, pull requests and agent titles. All stages filters by Jira's own grouping (to do / in progress / done), Needs action keeps only rows waiting on someone, and Hide finished drops tickets whose work is all merged. ↻ Refresh asks Jira and GitHub again straight away.

Answers are cached for a minute and a half and every call has a deadline, so the board polls cheaply and a slow network leaves a column empty instead of hanging the pane.