Every small team runs on a layer of invisible manual labour that nobody put on the roadmap. Someone reassigns a ticket the moment a PR opens. Someone drags a card to "In Review" because the author forgot. Someone pings the reporter to say "hey, this needs a reproduction step before we can look at it." None of it is hard. All of it is a tax — a few seconds of attention, dozens of times a day, spread across people who'd rather be building.
That's the work automation is actually for. Not a sprawling machine that runs your team for you, but a handful of rules that remove the small, repeated decisions nobody should have to make twice. The goal isn't to automate everything. It's to automate the things that are so predictable a human doing them is a waste.
This post is about picking those things. What's worth a rule, what isn't, and how to think about it so your board stays honest instead of quietly drifting into a state nobody trusts.
Start with the rule that removes a decision, not a person
The instinct when you first open an automation panel is to look for a big win — some heroic rule that eliminates a whole meeting. Resist it. The best first automations are boring: they take a decision that's already deterministic and stop making a person confirm it.
"When a pull request is linked, move the issue to In Progress." Nobody was ever going to say no to that. The card is in progress the moment code is being written; the only question was whether someone would remember to reflect it. A rule that encodes an obvious truth costs nothing and pays out every single day.
Compare that to a rule that tries to make a judgement — "auto-close issues with no activity for 14 days." That one has an opinion, and opinions on a board turn into surprises. Stale isn't the same as done. Start with the rules where the right answer is never in dispute, and you'll build trust in the system before you ask it to do anything clever.
The four pieces of a workflow rule
your.team's Automation module is built from four building blocks. You don't need to master all of them on day one, but knowing what each does tells you which problem it solves:
| Piece | What it does | Use it for |
|---|---|---|
| Custom statuses | Extra columns beyond the defaults | Making a real step (Blocked, In QA, Waiting on customer) visible instead of hidden in a comment |
| Transition rules | Control which status can move to which | Stopping a card from jumping straight from Backlog to Done and skipping review |
| Validators | Conditions that must be true before a transition | Requiring an assignee, an estimate, or a reproduction step before work can start |
| Post-functions | Actions that fire after a transition | Auto-assigning, stamping a timestamp, notifying the reporter — the "next thing happens on its own" part |
Read them in that order and a pattern appears. Statuses describe your process. Transitions and validators protect it. Post-functions do the busywork it used to generate. Most useful automations are one validator plus one post-function: require this before the move, then do that after it.
Automation is still in beta, so treat it as a place to codify the handful of rules you already enforce by hand — not to rebuild your entire process in a weekend.
What to automate first
If you want a ranked list, here's the order that gives small teams the most relief for the least risk:
- Auto-assign on transition. When a card moves to "In Review," assign it to whoever owns review — or back to the author when it bounces. This kills the "who's got this?" question at exactly the moment it's most expensive.
- Require the essentials before "In Progress." A validator that demands an assignee and an estimate before work starts means your reports are built on complete data instead of half-filled cards. Garbage in, garbage burndown.
- Reflect linked work automatically. Branch created, PR opened, PR merged — let the status follow the code. The board stops lying about what's actually happening, which is the whole reason a board exists.
- Notify the right person, not the whole channel. A post-function that pings only the reporter when their issue is resolved beats a firehose of updates nobody reads. It also keeps your notifications meaningful instead of trainable-to-ignore.
- Enforce the exit gate. A transition rule that blocks Done until the card has passed through review or QA is the cheapest quality control you'll ever ship. It's a spreadsheet formula for your process.
Notice what's not at the top: nothing that guesses intent, nothing that closes or deletes work, nothing that emails a customer. The early wins are all about reflecting reality faster and refusing to let incomplete cards move forward.
What to leave manual
Automation earns trust by being predictable, and it loses it the moment a rule does something surprising. Keep a human in the loop for anything that involves judgement or is hard to reverse:
- Priority changes. What's urgent is a conversation, not a trigger.
- Closing or archiving work. "No activity" is not a synonym for "resolved." Let people close their own cards.
- Cross-team handoffs. A rule that flings a ticket into another team's backlog without context just moves the confusion downstream.
- Anything that messages people outside the team. Customers and stakeholders deserve a human's phrasing.
A good test: if you'd want to double-check the outcome, don't automate it — or automate the setup (assign, label, notify) and leave the decision to a person.
Automation is a board-hygiene tool, not a headcount tool
The mistake teams make is thinking automation is about doing more with fewer people. It isn't. It's about keeping the shared picture of your work true without anyone babysitting it. A board where the status always matches reality is worth more than any dashboard, because every other thing you do — WIP limits, sprint planning, forecasting, standups you can finally cancel — is built on top of it.
Start with two or three rules that encode truths you already enforce by hand. Live with them for a sprint. Add the next one only when you catch yourself doing the same manual step for the tenth time. Automation done this way never feels like a system running your team; it feels like the team finally stopped repeating itself.
Ready to stop dragging cards for people? See what Automation can do — trigger-based rules, validators and post-functions, on every plan. Check the pricing, then start free and codify your first rule today.
