Skip to main content

​
Ticket Manager

Ticket Manager owns one delegated ticket from intake through implementation. It is available in Linear, Jira, and GitHub Issues variants. Each variant keeps one canonical status comment up to date as work moves through four milestones: started, workers dispatched, pull requests or merge requests opened, and terminal. Before implementation starts, Ticket Manager verifies that the ticket establishes the concrete problem, desired outcome, implementation scope, and target repositories. It consults linked evidence when available and remembers durable guidance within the relevant Linear project, Jira Epic, or GitHub repository. A delegation trigger requests triage; it does not bypass this readiness check. If material product intent or scope is unresolved, Ticket Manager writes a specification, links the session from the ticket for human review, and waits. Once the work is ready, it normally launches one PR Author worker per target repository. It links every opened change back to the ticket and closes the ticket only after all expected changes are merged or otherwise terminal.

​
Delegating tickets

  • Linear: Delegate the issue to Augment through a Linear Agent Session, or provide an issue URL or identifier directly.
  • Jira: Add the configured delegation label, or provide an issue URL or key directly. Ticket Manager never changes Jira labels; remove and re-add the label to retry an automated run.
  • GitHub Issues: Add the configured delegation label to an issue in an allowed repository, or provide an issue URL or repository-qualified number directly. Ticket Manager removes the label after claiming an automated run so later updates do not create duplicate sessions.
  • Best for: Teams that want implementation to begin from an explicit ticket delegation while preserving a readiness gate, human review for underspecified work, and tracker-native lifecycle updates.
  • How to use: Connect your ticket tracker, configure repository routing and a PR or MR Author worker, then delegate a ticket using the platform-specific method above. Direct implementation is available only when the Expert has complete change-authoring instructions configured as a fallback.

​
See Also

  • PR Author — the worker Ticket Manager normally launches for implementation.
  • Project Builder — use when a larger feature first needs design and a ticket breakdown.
  • Understanding Automation — how ticket events launch Ticket Manager sessions.