When you onboard with Auto Qelos, work doesn't happen by emails or "got a sec?" chats — it happens on your task board. Tickets flow through a fixed set of statuses, and each ticket carries a tag that tells us which product the work belongs to. Get those two things right and your delivery just runs. Get them wrong and even simple tickets stall.

This is the short version of how every successful Auto Qelos client manages their board.

The Five Default Statuses

Every Auto Qelos task board ships with the same five statuses by default. They're set up when your product is provisioned, and our automation reads them by name — so renaming or skipping a status on your side will break the flow.

If these names don't fit how your team thinks about work, that's fine — just ask us and we can configure custom status names for your product. The five below are simply the defaults we use everywhere unless you tell us otherwise.

Open 3 promoter pillow-maker Pending 2 awaiting your reply promoter In progress 1 pillow-maker Review 1 promoter Closed 2 promoter pillow-maker

The standard Auto Qelos workflow — every ticket moves left to right.

  • Open — The default state for a new ticket. You've described what you want; Jacob hasn't picked it up yet. This is where every new request starts.
  • Pending — Jacob has read the ticket and asked a follow-up question. The board is now waiting on your answer. Until you reply in the ticket comments, nothing else will happen on it.
  • In progress — Jacob is actively working the ticket. Code is being written, a branch is open, a PR is on the way.
  • Review — The work is complete and waiting for your review. Open the PR, click the preview link, and either approve it or leave change requests in the ticket.
  • Closed — Done. Merged. Shipped. Don't reopen closed tickets — create a new one for follow-up work so the history stays clean.

"Pending" Means: I'm Waiting on You

The status that trips up most clients is Pending. It looks similar to Open, but the meaning is very specific: Jacob asked you a follow-up question, and the ticket is blocked until you answer it.

If you check your board and see anything sitting in Pending, that's your queue — those tickets need your input before anything else can move. The longer a ticket sits in Pending, the longer your delivery is on hold. Treat the Pending column like an inbox: clear it daily.

Tag Each Ticket With the Product Name

This is the second rule, and it's the one most clients get wrong on day one. You don't assign Jacob as a user, and you don't @-mention him. You add a tag to the ticket with the name of the product the work belongs to — for example, if you want work done on your promoter product, you add a tag named promoter to the ticket.

The product name is the slug we set up when your account was provisioned — for example, promoter, pillow-maker, or foody-app. That tag is what tells our automation which repository, branch, and AI agent should pick the ticket up.

CLOSED make the website green TAGS accepted promoter Tag = product name Add the product name as a tag so Jacob picks it up.

A real ticket: the promoter tag is what routes the work.

A ticket with no product tag has no destination — it sits on the board until someone manually triages it. A ticket with the wrong product tag goes to the wrong codebase. Two simple rules:

  • Every ticket gets exactly one product tag. No tag means the ticket is invisible to automation. Multiple product tags create ambiguity.
  • Use the exact product slug, lowercase, no spaces. If your product was set up as promoter, the tag is promoter — not Promoter and not The Promoter App.

A Day on the Board

Here's what a healthy day on your board looks like:

  • Start the day by checking Pending. Anything there gets answered first.
  • Glance at Review. Anything there is ready for you to test and approve.
  • Add new tickets to Open, with the product tag already set, and a clear description of what you want.
  • Jacob's automation handles the rest — picking tickets up, asking follow-ups, opening PRs, and moving them to Closed.

Common Mistakes to Avoid

  • Adding extra statuses like "Blocked" or "On Hold" without telling us. Our automation only knows the statuses configured for your product. Use ticket comments to flag a hold — or ask us to set up additional statuses if you need them.
  • Assigning Jacob as a user instead of tagging the product. Jacob isn't a developer you're assigning work to — the product tag is the routing key.
  • Leaving Pending tickets unanswered for days. Every day a ticket sits in Pending is a day of delivery you've already lost.
  • Renaming statuses in the board UI. Our automation reads them by name, so an ad-hoc rename will break the flow. If you'd prefer different names, just ask us — we can configure them for your product.

That's the Whole System

Five statuses. One product tag per ticket. An eye on the Pending column. Manage your board with those three habits and your Auto Qelos delivery will run at the pace it's designed to run.

If you're not yet on Auto Qelos and want to see this workflow in action — including the AI-powered development team that picks up tickets and ships PRs while you sleep — register today and we'll get your board set up for you.