Part

Ticket tracker

You might say: issue tracker, work board, backlog, project board

A service that records work items and their state. It is the factory's durable queue and its human-facing record.

What it does

Holds the task request, ownership, routing state, and links to discussion so runs can return to the same work.

Ask

Can a run find one clear task, update its state, and leave a useful record for the next run?

Typical

Built into a git host, a dedicated tracker, a self-hosted tracker, a general work tool, files in a repository, or a custom service.

Trouble

Tickets are duplicated, stale, unowned, or routed to a task that cannot act on them.

What to look for

1. Board columns or status pills
2. A ticket detail page with title and body
3. Assignee, labels, and activity controls

Parts

• Ticket: A work item that records a request, its state, its owner and its discussion, and scopes one session of work.
• Ticket source: Something outside the tracker that supplies a request or observation.
• Routing label: A label or status value that tells the factory which task may handle a ticket.
• Comment thread: The ordered conversation attached to a ticket or pull request.

Catalogue: Tracker type

• Git-host built-in: Issues live beside the repository, pull requests, labels, and checks on one host. The tracker shares the code host's identity and event stream.
• Developer tracker with agent API: A dedicated development tracker exposes agents as workspace actors that can be assigned issues and write comments. The tracker gives an agent a first-class identity and delegation path.
• Self-hosted open source: A tracker is run and operated by the team that owns the factory. The team controls its deployment, storage, and integrations.
• General work tool: A broad work-management product stores work items and can react to their changes. The product exposes task events that automation can consume.
• Tickets as files in the repository: Each request is a versioned file or record next to the code. The repository itself becomes the durable task store.
• Build your own: A small service owns its records and emits change events. Its records can emit events that downstream automation consumes.

Connections

• See also: Git host
• See also: Comment thread

Sources

1. GitLab, Issues, IssuesIssues help you collaborate with your team to plan, track, and deliver work in GitLab.
2. Linear, Getting Started with Agents, Agent session lifecycleSession state is visible to users, and updated automatically based on the agent's emitted activities.

Use it on your project

teardown-apply: hold "Ticket tracker" (ticket-tracker) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal