User GuideBoard automation

Board automation

Let the board do the routine steps for you: start tickets from templates, create regular tickets on a schedule, run automations when things change, watch time in status and client SLAs, and draft release notes from done tickets.

Templates · Recurring tickets · Automations · Slack & client e-mail · Time in status · Client SLAs · Release notes

User GuideBoard automation

Board settings

Open a board and choose Board settings in the board header. The menu shows the tools your group lets you use: Ticket templates, Recurring tickets, Automations and Client SLAs. Each one belongs to that board. Standard and up

Ticket templates

Templates are starting points for tickets you write again and again — a bug report, a new starter checklist, a monthly check.

New template

Board settings → Ticket templates → New template. Give it a name.

Fill it in

Add a title that new tickets start with, the type, priority, a description (for example “Steps to reproduce / Expected / Actual”), labels, checklist items and sub-tasks (one per line).

Use it

When you create a ticket, click Use a template above the title and pick one (type to search when there are many). It pre-fills the create panel and keeps any title you already typed; labels, checklist items and sub-tasks are added when the ticket is created.

Recurring tickets

Recurring tickets are created on a schedule, so regular work never slips. They show a small Recurring badge on the board.

Schedule	Example
Every weekday (Mon–Fri)	Daily stand-up notes
Weekly on chosen days	Weekly client report every Friday
Monthly on a day	Invoice check on the 28th — short months use their last day

Set the ticket title, who it's assigned to and an optional end date.
Pick a template to add its checklist and sub-tasks to every ticket it makes.
Choose the timezone the time follows: your company's timezone (the default), the assignee's local time from their profile, or any timezone you pick — so 9:00 means 9:00 for the person doing the work.
Deleting a recurring ticket stops new ones; tickets it already made stay.

Automations

An automation is a simple rule: when something happens, if the ticket matches, then do one or more things.

Automation

When

Status changes to Done

Type is Bug, priority High

Then

E-mail the client contact · Post to Slack

When (trigger)

Status changes (optionally from / to a column), a ticket is created, the assignee changes, the priority changes (optionally to a priority), or the due date passes.

If (optional)

Only for certain priorities, ticket types, or tickets that have any of the labels you list.

Then (actions)

Move to column, assign to someone, set priority, add a label, add a comment, notify people in the app, e-mail the client contact, or post to Slack.

Run log

The Run log tab lists what your automations did and when, so you can check they're working.

Changes made by an automation never start other automations, so rules can't loop. Turn a rule off with its switch without deleting it. Post to Slack uses your company's Slack connection and is skipped if Slack isn't connected.

Time in status

Open a ticket to see Time in status: how long it has spent in each column so far. Use it to spot where work waits — for review, for a client, or for testing. You can also turn on the column age on cards to see how long each ticket has been in its current column.

Client SLAs

Set response and resolution targets for tickets your clients raise in the client portal. Hours run around the clock.

Set the targets

Board settings → Client SLAs. Pick a project and enter First response (hours) and Resolution (hours).

Watch the timers

Client tickets in that project show a countdown chip on the card that turns amber, then red, as the deadline gets close. The ticket shows its Client SLA too.

Review the results

The SLA report in board Reports shows client tickets with an SLA for the last 7, 30 or 90 days — met, missed and running, by priority.

Client SLAs work with the client portal, which is part of Premium and Enterprise.

Release notes from tickets

Open a saved release in the board's Releases view and choose Draft from tickets. TeamTrackin writes the notes from the done tickets in that release, grouped into features, fixes and improvements, and leaves internal tickets out.

When AI is turned on for your account, Improve with AI rewrites your draft in plain, client-friendly language. If it can't, your draft stays exactly as it was. Edit anything before you save.

Ticket layout & custom fields

Every team tracks slightly different things. You can shape the ticket view around how your team works, with optional sections and your own custom fields. The automation builder also offers ready-made templates to start from and an audit log, so you can see what changed and when.

Person fields show the person's picture and name, on the ticket and on the card.
History lists every custom field change: who changed it, when, and the old and new value.
The board's Fields filter lists all your dropdown, person and checkbox fields, with search, however many you have.
Sections you turn off are hidden in the client portal too, so clients see the same layout.

Who can do what

Admins set these in Company → Groups & permissions → Board. They only apply on boards the person can open.

Permission	Lets people
Ticket templates	Create, edit and delete the board's templates (everyone with board access can use them).
Recurring tickets	See, create, edit and delete recurring tickets.
Board automations	See automations and their run log; create, edit and delete them.
Client SLAs	View SLA timers and the SLA report; Edit sets the targets.
Releases	See releases; create, edit and draft release notes.

PreviousIntegrations & Import

Next guideProjects

Spend less time moving tickets

Board automation is included from the Standard plan. Open Board settings on any board to start.

Try the demo

Cookies on TeamTrackin