Concepts

Overview

A few ideas explain most of AoTwin. This page defines them in the order you meet them. Each one links to the page that goes deeper.

Workspace

A workspace is your team’s home in AoTwin. It holds the people, the projects, the tickets and the plan. You name it when you sign up, and the sidebar shows its name at the top. If you belong to more than one workspace, switch between them from that menu.

Every person in a workspace has a role, either Admin or Member. Admins change settings. Members see all the work and can ask for changes. See People.

Project

A project is a group of tickets, usually for one product or one repository. Every ticket belongs to exactly one project. When you connect GitHub, each repository you choose becomes a project, so AoTwin knows which code a ticket should change. A project without connected code still works as a place for tickets.

The sidebar lists your projects once you have more than one. See Projects.

Ticket

A ticket is one piece of work: a title, a description, and everything that happens to it after. The app calls a ticket a request in some places, for example New request and My requests. They are the same thing. This documentation says ticket and keeps the app’s wording for button and page names.

See Tickets.

Key

Every ticket has a key: a project key, a dash and a number, like WEB-12. The key appears on the ticket, on the board and in links, and a key written in a description or comment links to that ticket. Tickets in the project every workspace starts with use AO, as in AO-1. If your workspace is connected to Linear, a ticket sent to Linear takes Linear’s key, and the old key keeps working.

Status

A status says where a ticket stands. A ticket you or a teammate holds moves through Backlog, Todo, In progress, In review and Done, or ends as Canceled. A ticket AoTwin holds shows AoTwin’s own steps, such as Working, Waiting for review and Handed back. See Statuses.

Assignee

The assignee is who holds the ticket. It can be:

• A person in the workspace.
• AoTwin, the agent. It starts work only when a ticket is assigned to it.
• Nobody. The ticket waits in Backlog until someone takes it.

Filing or editing a ticket never starts AoTwin. Assigning it does.

Asker

The asker is the person who asked for the change. It is usually whoever filed the ticket, but you can file a ticket for someone else by choosing them under Who asked. The asker gets the updates for the ticket in their Inbox, and can edit or close it. Admins can too.

AoTwin, the agent

AoTwin is also a teammate you assign tickets to. It reads the ticket and your code, makes the change, runs your team’s checks and opens a pull request. If something is unclear, it asks a question on the ticket instead of guessing. It can’t approve or merge anything: every change waits for one of your engineers.

Assigning a ticket to AoTwin needs a paid plan and, for code changes, a connected GitHub. See pricing.

Credits

Credits are what AoTwin uses up while it works on a ticket. Each paid plan gives the workspace a monthly allowance, and the Plan page in settings shows how much is used. A ticket’s page shows the credits it has used, with a running count while AoTwin works. A ticket AoTwin hands back costs half of what it used. See Credits and pricing.

Inbox

Your Inbox collects updates about tickets you asked for, and anything waiting on you, like a question from AoTwin. See Inbox.

Ask AoTwin

Ask AoTwin is a chat that answers questions about your team’s tickets and can draft new ones for you to confirm. It is separate from assigning a ticket. See Ask AoTwin.