Card templates and bulk edit
A template is a card that makes cards: a Bug with its repro steps, a Release with its checklist. Bulk edit changes all the cards you pick in one go, with one Undo.
Make a template
A template is either the whole workspace’s or one team’s. A team’s templates serve its sub-teams too.
- For every team: open Settings → Workspace, and click Edit on Card templates for every team. For one team: search Settings for Card templates, choose the result marked Each team › Templates, and pick the team.
- Click New template.
- Fill in what a new card should get:
- Name, which you pick it by
- Title, where
{{title}}is what you type and{{date}}is today - Notes, Recipe, Labels, Priority and Estimate
- Fields, for a team template’s custom fields
- Sub-tasks, one a line
- Click Add template.
Owners and admins make and change templates; everyone who sees the team can use them.
Make a card from a template
- In the board’s quick add, click New from template… and pick one. The list shows the column’s team’s templates, its parent teams’, then the workspace’s.
- In Start work, use the Template pill, or start your sentence with the template’s name:
bug: login fails. - From a terminal:
andon add --template bug "Login fails" -t Web. - From a capture request, with
template.
What a template fills
- The title comes from the pattern, the notes are added after any notes the card has, and the labels are added.
- A recipe, priority, estimate or field value is set only where the card has none. A template picks a recipe; it never replaces one.
- Each sub-task becomes a card under the new one, in the Backlog, in order, with the same team, project and priority. These sub-tasks never start on their own: you move or run each one. A card that is already a workstream step can’t have sub-tasks, so it gets them as a checklist in its notes instead.
Fill every card that lands in a status
A team status can fill each card that lands in it from a template.
- Search Settings for Team statuses.
- On a status, set A card landing here gets to a template.
Every card that lands in that status is filled from the template once, however it got there: moved by a person or by Andon, made there, or moved in from another team. Moving it out and back doesn’t add the notes or sub-tasks again.
Change many cards at once
Pick the cards
On the board or in the List layout:
Xpicks the selected card.- Shift-click picks a card; while picking, a plain click picks more.
- ⌘A (Ctrl+A) picks every card in the selected card’s column, or every row in the list.
- Select in the toolbar starts picking.
On the phone, tap Select beside the column chips, then tap cards. The bar sits above the tabs.
The selection bar
| Button | Does |
|---|---|
| Move to | moves the cards to a column |
Set (E) |
sets one of: Status (when the picked cards’ teams have statuses; looked up in each card’s own team), Priority, Labels… (add and take off), Cycle, Milestone, Estimate, Field (when a picked card’s team has fields) |
| Run | gives each card its own run, as R does for one. A workstream starts its steps; a card on a team with Autopilot goes to Ready instead |
| Group | builds the cards together: one branch, one pull request |
| Archive | archives the cards, after asking |
× (Esc) |
clears the selection |
The bar can’t change a card’s owner, project, due date or parent. Change those one card at a time.
What happens to cards you can’t change
Set and Archive change each card as if you edited it alone. Andon skips a card if it’s someone else’s, you can’t see it, its team has no such status, or it can’t take the value. The rest still change. The toast says how many and why: 3 of 5 changed; 2 are Sam’s.
One Undo in the toast puts every changed card back. A field’s Undo puts back only that field. The audit log keeps one entry for the batch.
Move to and Run go card by card, with the same questions a single move or run asks, such as whether to stop work in progress. A status set from Set moves the card to that status’s column without those questions.
