/next/ai/tickets) opens Tickets, where every piece of Ankra AI’s work is a ticket with an owner, a next step and a record of what happened. The Ankra agent picks tickets up, investigates, drafts a plan, has it reviewed where you require it, and waits for a person to approve before it changes anything in production. You follow the work, decide at the gates, and close the loop.
To turn the ticket desk on and work a first ticket end to end, follow Set up the ticket desk and work tickets with the Ankra agent. This page explains how the board works.
The ticket lifecycle
A ticket has one of these statuses:
The board groups tickets by Lifecycle unless you choose otherwise, in these lanes:
When you close a ticket yourself, the Resolution is Fixed, No Action, Duplicate, Wont Fix or Escalated. Ankra records three more on its own:
Closing a ticket as Fixed without a Verification observation is recorded as your own word, not as a fix the platform verified.
Where tickets come from
- Health checks - problems Ankra AI finds on its own are filed at the severities you choose under Automatic insight tickets on the ticket desk. See AI Insights.
- Alert remediation - when an alert fires and auto-remediation starts, an incident ticket tracks it, and it closes itself when the alert clears. See Alerts.
- Known Ankra issues - when an alert comes from a problem in Ankra itself rather than your cluster (an Ankra service failing, Ankra’s registry erroring, the cluster agent’s credential refused by Ankra), Ankra engineering gets the problem and your board gets a ticket titled
Known Ankra issue: ..., labelledknown-issueandplatform-owned. It is parked at Blocked, no agent works it, nothing on the cluster is changed and no question is asked of you. It closes itself asno_actionwhen the alert clears, and reopens if the problem returns. - Automations - an automation that reaches an approval gate files a ticket straight into Awaiting Approval. See AI automations.
- People and agents - New ticket on Tickets, Create an Ankra AI ticket in Find, or the
file_tickettool from a chat or MCP session, including your own agent. - Chat fixes - when a person applies a gated write on a cluster through the AI chat or an MCP client (a Stack draft, a scale, a restart), Ankra records it on a receipt ticket labelled
chat-fix, one per conversation, with every action recorded as a change. Receipts are an audit trail of your own actions, so they stay off the board: its views, its counts andticket_listleave them out. A receipt keeps its number and timeline and opens from a link, and the ticket list API returns receipts when asked withinclude_receipts=true.
How the agent works a ticket
A ticket’s Work mode is Automatic staffing or Manual task. Ankra assigns an automatic ticket in Triage to an agent that may work board tickets, preferring one scoped to the ticket’s cluster. With no agent available, the ticket goes to a person instead of waiting silently. A manual task stays with your team: no automatic staffing, mirroring or escalation. On the ticket desk (Ticket desk on Tickets) the agents that may work tickets show as one Ankra agent, Available for automatic staffing or No eligible agent reported. The portal cannot change which agents those are. See Agents that work tickets. Commenting on a ticket wakes the agent working it, even while the ticket waits at Awaiting Approval, so a comment is how you steer it mid-flight. Only a person’s comment does this: a comment a model writes, from the AI chat or an MCP client, is recorded on the timeline but does not wake the agent. Write it under Add context on the ticket’s Timeline tab.Follow the agent’s runs
A ticket’s Work tab lists its Agent runs. Read run activity shows what a run did, step by step. View run details opens the run’s own page, and Request stop for this run stops a run that is still going. A link to a ticket with a run in its address opens that run, marked Selected run · Ankra agent. See Follow, steer and stop an agent run.The ticket page
A ticket opens on Overview, with Evidence, Plan, Work and Timeline beside it. The ticket also shows its Properties (Owner, Priority, Environment, Work mode, Labels) and its Connected work.Is it still happening?
An open ticket says in one sentence whether what it is about still holds, for example Still happening: the alert is firing., No longer happening: the alert stopped firing. You can likely close this ticket., or Not checked again automatically since it was filed. Check before acting. When the cluster cannot be read, the sentence says why, such as Cannot check: the cluster was removed from Ankra. Check before you approve work on a ticket whose problem may be gone.Plans, review and approval
The plan is the contract between the agent and you:- The agent drafts a plan on the ticket’s Plan tab. While the ticket is Planning and has a plan, Request independent review sends it for review.
- With Require an independent plan review ticked and a working reviewer agent (
ankra ai tasks templates hire reviewer), the plan is reviewed in a pass separate from the work pass. With no reviewer set, the tick does nothing. An agent cannot approve its own work. - The ticket waits at Awaiting Approval. Review and decide opens the review: choose Approve or Request changes under Decision, add a Review note, and press Approve and release work or Request changes. Requesting changes sends the ticket back for the agent to revise the plan with your note.
Production changes
Approving a plan does not widen what the agent may do. Each production change beyond its autonomy still asks on its own, under Proposed production changes on the ticket’s Overview and in Needs you. Each change shows its risk and whether it is Reversible or Rollback not guaranteed. Tick I reviewed this specific production change., then press Approve this change or Reject change. Changes proposed together are decided at once, with Approve all or Reject all followed by their number. Where Ankra cannot show exactly what a change does, only rejecting it is offered on the ticket.Answering a choice
When what blocks the ticket is a choice - the agent found more than one way forward and needs you to pick - the ticket opens on the agent’s question under Needs you, with the options it offered and the one it recommends marked Recommended. Nothing is pre-selected. Pick one and add Additional context if you want, or choose Another answer and write Your answer. Send decision to Ankra records your answer on the timeline as a comment starting withDecision: and hands the ticket back to the agent, which resumes from your answer without asking again. A ticket that leaves Blocked for any other reason drops the question.
The same choice is offered everywhere the ticket reaches you:
- AI chat and MCP -
ticket_getshows the pending question underdecision_request, and theticket_decidetool records your answer (“go with option A on T-8”, or “tell T-8 to publish to both for a week”). Ankra records the answer as relayed by you and does not check that a person chose it, so ask the assistant to relay your decision rather than to pick one. - CLI -
ankra tickets get T-8prints the options with their keys and the recommendation;ankra tickets decide T-8 --option apicks one,--answer "..."answers with something else, and both together record the option with your note.ankra tickets listshows which tickets wait on your decision. - Slack and Teams - the thread reply that announces the block carries the options as buttons (the recommended one highlighted), and so does the escalation card while the ticket still waits. Clicking an option records it as your decision. Something else asks you to reply in the thread starting with
Decision:- that reply is recorded as the answer rather than as a plain comment. - API -
POST /api/v1/org/ai-tickets/{ticket_id}/decisionwithoption_key(one of the offered keys) and/oranswer(required when no option is chosen). A ticket that is not waiting on a choice answers409.
Recorded changes
Every write an agent or the chat applies on a ticket’s behalf is a change on the ticket, listed under Recorded changes like a commit log. Each entry names its status, the cluster and Stack it touched, its risk and whether it is reversible, and the operation it created on the cluster’s operations ledger, or No execution is linked to this change. The verdict follows the operation, not the tool’s reply: a change whose apply is still running reads as applying, and one whose apply failed afterwards reads as failed. The same ledger is on the API at/api/v1/org/ai-tickets/{ticket_id}/changes.
When a person is needed
A ticket needs a person when it is Awaiting Approval, Blocked, or Awaiting Review with a plan the review already approved. The Needs a human filter on Tickets shows exactly those, and Needs you lists them with every other decision waiting on a person. When a ticket becomes blocked or goes stale, Ankra raises an AI ticket needs a person notification and records the escalation on the timeline. A plan reaching Awaiting Approval raises Plan for ticket T-<number> awaits your approval. Both link to the ticket. Route them with notification routing.Conditions
A condition is one problem that keeps happening to one thing on your clusters. Every ticket Ankra files for an alert or an insight belongs to its condition, so you can see how often the problem came back and how each ticket ended. Conditions on Tickets opens them (/next/ai/conditions).
The list shows each Condition, How often it was seen, its open Ticket and when it was Last seen. Keep coming back shows only the conditions closed three times in a row without anything being changed, marked Keeps coming back. Such a problem needs a lasting fix, not another ticket.
A condition’s page shows What happened (each Ticket filed, Ticket closed, Check run, Playbook run and Decision), every ticket filed on it with How it ended, and its details.
Slack and Teams threads
Choose a Slack or Teams destination on the ticket desk’s Communication tab and each new automatic ticket opens its own conversation there: timeline events post as replies, and replies in the thread land back on the ticket’s timeline, waking the agent. An escalation carries Assign to me and, while a plan waits for a verdict, Approve plan and Request changes; a ticket blocked on a choice carries its options as buttons and Something else (see Answering a choice). Manual tickets are not mirrored. See Set up the ticket desk.Project channels
A project can have its own Slack channel and Teams conversation for ticket threads. A ticket of that project then opens its thread there, with the same approval, plan and decision buttons. The organisation’s channel is the fallback, per provider: a project with only a Slack channel still posts to the organisation’s Teams conversation. Set them under Project channels on the ticket desk’s Communication tab, or from the CLI:core and tools, give core the channel #ankra-core and tools the channel #ankra-tools. Add one routing rule per project for its other notifications; see one channel per project.
The Ankra bot’s answers in a project channel still come from your default project, and remediation approval cards still go to the organisation’s Slack remediation destination.
Mirroring tickets into your own tracker
A sync connection mirrors tickets outbound to a Jira project, a Linear team, or your own webhook endpoint: the external issue is created once per ticket, and timeline events follow as comments. Filters decide which kinds and priorities travel. Sync is one-way - status changes arrive as comments, and nothing done in the tracker comes back to the board. The portal has no page for sync connections; set them up withankra tickets sync connections create. See Sync tickets to Jira, Linear or a webhook.
Views
Saved views are kept in your browser, so they do not follow you to another browser or device.
Working the board from your own tools
The board is not tied to the portal. Every surface works the same tickets with the same gates:- CLI -
ankra ticketslists, reads, comments on, moves and decides tickets from a terminal. - Your own agent - Claude Code, Cursor, Codex or an agent you wrote can pick up tickets over MCP, investigate, draft a plan and carry it out once you approve it. See Work the AI board with your own agent.
- Slack and Teams - the ticket’s thread, described above.