Automate the busywork in your issue tracker
Every team does the same small chores hundreds of times a year. Here are the rules that delete that work permanently.
Think about what your team does immediately after moving a ticket to Done. Unassign it, maybe. Remove the "in review" label. Close the linked subtask. Each takes four seconds, and each happens hundreds of times a year, and none of it requires a human.
How when-then rules work
VectorKan's automation is deliberately simple: pick a trigger, pick an action. No scripting, no builder canvas, no learning curve. Rules fire on ticket creation, status changes, assignment and labelling.
Rules worth setting up today
- When an issue moves to Done, unassign it. Keeps everyone's "my work" list honest, so it shows what's actually in flight.
- When a Bug is created, add the triage label. Guarantees new bugs land in your triage filter instead of drifting.
- When an issue moves to In Progress, assign it to whoever moved it. Removes the "who's doing this?" ambiguity that stalls work.
- When an issue is created with Urgent priority, add a label your alerting filter watches. Turns priority into something the team actually notices.
- When an issue moves to Blocked, unassign it. Blocked work shouldn't count against someone's active load.
The rule to be careful with
Auto-assignment based on anything other than "who touched it" tends to go wrong. Round-robin assignment in particular looks fair and produces a mess — it ignores who's already loaded, who's on holiday, and who actually knows that part of the system. Let people pull work; automate the tidying around it.
Automation as documentation
A quietly valuable side effect: your rules describe how your team actually works. A new starter reading "when moved to Done, unassign" learns something real about your process in one line — faster than any onboarding document, and guaranteed to be current because it's executing.
Keep the list short for the same reason. Five rules everyone understands beat twenty nobody can explain, and when a ticket behaves unexpectedly the cause should be findable in seconds.
Where to start
Watch your own board for a week and note anything you do more than twice in the same circumstances. That list is your rule set. Most teams find three or four, set them up in about ten minutes, and never think about that chore again.
Frequently asked questions
What can issue tracker automation do?
Handle the repetitive steps around work: assigning, unassigning, labelling and moving tickets when something happens. VectorKan uses simple when-then rules triggered by issue creation, status changes, assignment and labels — no scripting required.
What are good automation rules to start with?
Unassign when an issue moves to Done, add a triage label when a bug is created, assign to whoever moves an issue into In Progress, and unassign when something becomes blocked. Those four remove most of the routine tidying.
Should you auto-assign tickets to team members?
Be cautious. Round-robin assignment ignores current workload, availability and expertise, and usually creates more rebalancing work than it saves. Automate the tidying and let people pull work themselves.
How many automation rules should a project have?
Few enough that everyone can explain them. Five well-understood rules are more useful than twenty nobody remembers, because unexplained ticket behaviour erodes trust in the board.