Let cards move when the work happens

One switch: a merged pull request sends its card to testing, passing tests move it to done with the evidence, and a check failing later brings it back.

In short

"Move cards when the work happens" is one switch that makes three ordinary rules: merged work goes to testing, tested work is done, and failing work comes back. The card moves by itself and gets a comment with the evidence.

Before you start

• Who: only people who manage the board turn the switch on, and the three rules then run as that person.
• Plan: every plan. The tests run with that person's access and allowance in the module that holds them.
• First: connect the repository so merged pull requests reach the board (see /help/boards/board-webhooks-and-repositories), name a testing and a done column, and let a card follow a test that can run.

Steps

1. Open the board's settings and go to "Automation".
2. If the panel asks which columns play the parts, choose "Where work is tested" and "Where work is done". On a board made from a software template they are already known.
3. Turn on "Move cards when the work happens".
4. Fix anything the panel says is missing, until it says everything it needs is in place.

Result: cards move between testing and done as pull requests merge and tests pass or fail.

Good to know

• Only people who manage the board can switch it. Whoever switches it on is the person the three rules run as: the tests run with that person's access and allowance, and the comments are written in their name.
• While its tests are queued or running, the card's face says "Testing…".
• The three rules are listed with the board's other rules and can be changed or switched off one by one. Turning the main switch off stops all three. A locked card stays where it is.
• The switch is not offered on a board whose columns follow another module's stages, such as a hiring board.
• What happens next: a card that moves gets a comment with the evidence. Turning the main switch off stops all three rules at once.

The evidence comment

The comment states facts and never comes from AI. It names the rule. It gives the newest finished run of the card's linked tests: how many passed, failed or could not run, and when it ended. It counts how many of the records the card follows pass, fail or have no result, by kind and never named. And it gives the newest merged pull request that names the card, with its repository, reference, title and address, and the newest commit. It is marked as a rule's comment, and you cannot edit it. Its author or a board manager can remove it. The rule never writes the same evidence twice.

If something goes wrong

• No repository connected: the board never hears that a pull request was merged. Connect a repository - see /help/boards/board-webhooks-and-repositories.
• No card follows a test that can run. Open a card, go to Links and follow a saved request, a suite, a SQL case, a cache check or a UI track.
• A rule is missing: "Make the rules again" puts back the missing ones.
• The rules are paused because the person they run as can no longer change the board: "Take over" makes you that person.
• "Tested and done are two different columns of the same grouping.": choose two different columns.
• "This board's columns follow another module's stages, so this recipe does not move its cards.": the switch is not for a hiring board.
• "Choose the column where work is tested and the column where it is done.": name both before you turn the switch on.

Related

• /help/boards/board-rules
• /help/boards/links-and-checks
• /help/boards/board-webhooks-and-repositories