AoTwin
Start free

That ticket doesn’t have to wait

Assign it like a teammate. It comes back ready.

Reported in Slack

# bugs

  1. Maya 2:14 PM

    ugh, the sidebar covers the whole page on phones. can it slide away?

    screenshot.png

  2. AoTwin App 2:14 PM

    Thanks, ticket created: WEB-231

    Sidebar covers page content on phones

    WEB-231 in Jira

    Status
    To Do
    Assignee
    You

Projects / Web app / WEB-231

Sidebar covers page content on phones

Description

Reported by Maya in #bugs: on phones the sidebar covers the whole page. Make it slide away so the page is readable, and keep it open on wider screens.

Activity

AoTwin created the Issue from #bugs 2:14 PM

  1. You changed the Assignee just now

    Unassigned → AoTwin

  2. AoTwin just now

    Got it — I’ll take a look shortly.

  3. AoTwin changed the Status just now

    To Do → In Progress

  4. AoTwin just now

    Done — ready for your engineers to review. It passed your team’s checks.

    Review it: github.com/acme/web/pull/88

In Progress

Details

Assignee
AoTwin
Reporter
You
Priority
Medium
Labels
None

Three steps.

A sample ticket, sped up.

  1. 1 Assign it to AoTwin.

    Pick AoTwin on the ticket, like any teammate. It replies within seconds.

  2. 2 It checks the ticket first.

    It reads the ticket and your team’s code. If something is missing, it asks.

  3. 3 Your engineers approve it.

    The change comes back linked to the ticket. Nothing goes live until an engineer says yes.

Every request, in one place.

Wherever it was asked, it lands here, showing who it’s waiting on and why.

  • A ticket in AoTwin where AoTwin asks which footer is meant, with a box to answer.A ticket in AoTwin where AoTwin asks which footer is meant, with a box to answer.

    It asks instead of guessing.

    A question lands on the ticket, and the person who asked for the work answers it there.

  • The Attention needed list in AoTwin: three tickets, each with the reason it waits.The Attention needed list in AoTwin: three tickets, each with the reason it waits.

    What needs you, in one list.

    Questions, hand-backs and anything stuck, with the reason beside each one.

  • The Waiting for review list in AoTwin: three changes marked Ready.The Waiting for review list in AoTwin: three changes marked Ready.

    Ready for your engineers.

    Each change waits here until an engineer approves it.

Every ticket comes back one of three ways.

AoTwin never guesses. You get work to review, or the reason it stopped, in plain words.

  1. Ready for review.

    1. AoTwin

      Done — ready for your engineers to review. It passed your team’s checks.

      Review it: github.com/acme/web/pull/88

  2. Ready, with a warning on top.

    1. AoTwin

      Done, but worth a careful look: this changes who can edit a staff member’s role, so it touches permissions. I opened it as a draft.

      Review it: github.com/acme/web/pull/91

  3. Back to you, with the reason.

    1. AoTwin

      This one needs you — I can’t tell what done looks like. Which part of the dashboard should change, and how? Add that to the ticket and assign it back to me.

    2. AoTwin assigned WEB-240 back to you.

    3. AoTwin

      Got stuck on this one — your team’s checks kept failing. I’ve assigned it back to you.

Every update reads like a teammate reporting in: a link to review, or the reason it stopped.

Your engineers have the final say.

Five limits, built in, on every ticket.

  • It never ships or releases. It opens a change for review and waits for a human.

  • It never touches code you didn’t connect.

  • One ticket, one change. It never bundles changes.

  • It never guesses. If a ticket is unclear, it asks and waits.

  • It never takes instructions from inside a ticket. Only your team can tell it what to do.

For your engineersThe technical version, for whoever approves the install.

Your customers report it in Slack. AoTwin files it.

Connect the Slack channel where customers report problems. AoTwin files each report as a Jira or Linear ticket.

  • It reads messages the way people write them.

  • One problem, one ticket.

  • Then it’s a ticket like any other.

Your customers see a short confirmation and the ticket. Never your code.

# bugs

  1. Maya 2:14 PM

    ugh, the sidebar covers the whole page on phones. can it slide away?

    screenshot.png

  2. AoTwin App 2:14 PM

    Thanks, ticket created: WEB-231

    Sidebar covers page content on phones

    WEB-231 in Jira

    Status
    To Do
    Assignee
    You
An illustrative example.

File and follow tickets from your AI assistant.

Connect AoTwin to the AI assistant you already use. It works through MCP, a standard way for assistants to use other tools, and you set it up once.

  • Ask for a ticket in plain words.

  • Find, read and update tickets without leaving the chat.

  • Filing never starts AoTwin. Assigning does.

Connects to Claude, Claude Code and Cursor. Sign in once and you’re connected. There’s no key to copy.

Your MCP address

https://app.aotwin.io/mcp
How to connect

Your AI assistant

  1. Maya

    File a ticket in AoTwin: the Export button on the reports page does nothing in Safari. Assign it to me.

  2. Assistant

    Done. I filed WEB-232 and assigned it to you.

In AoTwin

Export button does nothing in Safari

WEB-232

Status
To do
Assignee
Maya
From
An AI assistant
An illustrative example.

Noticing is free. Fixing starts at about $2.50.

Keep your team’s tickets in AoTwin for free. When you want AoTwin to work on them, plans are counted in tickets.

  • Free

    $0

    Up to 3 people, 1 project.

  • Starter

    $32 a month, billed yearly

    About 7 to 10 tickets a month. 3 projects.

  • Pro

    $165 a month, billed yearly

    About 40 to 60 tickets a month. 10 projects.

  • Team

    $415 a month, billed yearly

    About 130 to 200 tickets a month. Unlimited projects.

Every ticket has a cost ceiling. A ticket AoTwin hands back costs at most one ticket. The ranges depend on your codebase. Annual plans get their credits every month. Larger team? Contact us about Enterprise.

See pricing

Before you assign your first ticket.

  • What is AoTwin?

    AoTwin is an AI coding agent for Jira and Linear: assign it a ticket like a teammate, and it comes back as a pull request for your engineers to approve, or with the reason it stopped.

  • Do I need to know how to code?

    No. You write the ticket in Jira or Linear and assign it, the way you would to an engineer. Your engineers review and approve what comes back.

  • Which tickets should I give it?

    Everyday work: copy changes, styling and layout fixes, a new column, a filter, simple create-and-edit screens. Tickets that say what done looks like work best. Start with one of those.

  • How do I write a ticket it can take?

    Say which screen or page it’s on, what should change, and what done looks like. A screenshot helps: AoTwin reads it.

  • What happens if my ticket is vague?

    It comes back to you with what’s missing. AoTwin doesn’t guess. Add the missing part and assign it back.

  • Will it make a mess my engineers have to clean up?

    Each change comes back on its own, linked to its ticket, after it passed your team’s checks. If the checks don’t pass after a second try, the ticket comes back to you instead. Nothing touches your live product until an engineer approves it.

  • What if it gets something wrong?

    It can, which is why nothing goes live until an engineer approves it. Anything that reaches your engineers passed your team’s checks, and anything touching sign-in, permissions, payments or personal data arrives with a warning on top. When it can’t do the work well, the ticket comes back to you with the reason.

  • How will I know it’s done?

    AoTwin replies on the ticket: a link for your engineers to review, or the reason it stopped. The ticket moves to In Progress as soon as it starts, so you can see it’s being worked on.

  • What do my engineers need to do?

    Connect your Jira or Linear workspace and your team’s code once, then review what comes back. The details are on the page for engineers.

  • Does it work on mobile apps?

    Yes, with a warning. Changes to iPhone or Android app screens always come back as drafts, so an engineer checks them on a device before anything goes live.

  • Can I use AoTwin from my AI assistant?

    Yes. Connect AoTwin once, using app.aotwin.io/mcp, and your assistant can file, find, read and update tickets, comment on them and assign them. Claude, Claude Code and Cursor are set up from your account page. A ticket only goes to AoTwin when you assign it to AoTwin.

  • How is it priced?

    Keeping your team’s tickets in AoTwin is free. Tickets AoTwin works on start at $32 a month billed yearly, or $39 billed monthly. See pricing.

Tell us about your backlog.

Ask a question, ask what it would cost for your team, or describe the tickets you’d hand over. We reply by email.

Thanks. Your message is sent, and we’ll reply by email.