Link cards, web pages and checks

Attach web links, relate cards to each other, and let a card turn red or green with the tests it follows.

In short

The "Links and tests" part of the card's "Related" tab connects a card to the rest of the work. That means web pages, other cards (blocks, relates to, duplicates) and checks from the testers. A card that follows checks turns red when one fails and green when they pass, and "Run linked tests" runs them.

Before you start

Who: adding or removing links needs "Change cards". Anyone who can open the board reads them, and a linked record shows only what you may see in its own module.
Plan: links are on every plan. Running a check uses your access and allowance in the module that holds it (API Tester, SQL Tester, Cache Tester or UI Tester).
First: save the request, case, connection or track you want the card to follow.

Steps

Open the card's "Related" tab and its "Links and tests" part.
Paste a full http or https address, add a label if you like, and pick a kind (Link, Document, Video, Recording or Design).
Choose "Add link".

Choose "Link a card".
Pick how it relates: "Blocks", "Blocked by", "Relates to" or "Duplicates".
Find the card by title.

Choose "Link a record".
Pick the "Record type" and find it by name. The list shows only what you can open.

Result: both related cards show the link from their own side; a card that follows checks shows their result.

Cards that follow checks

A card can follow an API Tester request, project, monitor, suite or verification, a SQL Tester case or project, a Cache Tester connection or a UI Tester track. When one starts failing, the card turns red and says how many checks fail. When every check with a result passes, it shows a green dot. Everyone watching the card is told when a check starts failing and when it passes again, and History records it - neither names the check.

Run the tests a card follows

"Run linked tests" appears above Linked records for anyone who can change the card, and on the red line at the top of an open card when a check fails. It runs every test you can run, as you: with your access, your plan and your allowance, exactly as if you pressed Run in each module.

A test you cannot open, or may open but not run, is not run; the record says why. Nothing is ever run as someone else.
A run your allowance has no room for is not run and never counts as a failure.
A UI track waits its turn in the UI Tester queue; the card waits for it and says so.
Monitors and verifications are not run from a card: a monitor checks on its own schedule.
When some tests failed last time, "Run the failing tests again" runs only those, so you can check a fix without running the rest. The run line then says it took only the tests that failed.
Each linked record shows a dot for each of the last runs that decided something - filled when it passed, a ring when it failed. "Flaky" marks a test whose result changed at least twice over those runs: it passes and fails without a change that explains it.

Good to know

Remove on a web link acts at once, and "Undo" adds it back. Someone who may only view the board can read links but not change them.
A blocked card says so on its face. "Duplicates" is how a bug is recorded as a duplicate.
Linked records show each result (Passed, Failed or Unknown), HTTP status code and duration. A record you cannot open shows as "Resource unavailable".
A result travels only inside the check's own workspace: a card on a team board that follows a personal project keeps the result it had when linked.
What happens next: following a check changes nothing in the other product. Watchers are told when a check starts failing and when it passes again.
To undo: remove a link from its row; "Undo" in the message adds it back at once.

What a card link cannot do

A link joins cards of one workspace: the same organization, or your own personal boards. A card of another organization cannot be linked.
"Blocks" cannot go round in a circle. When the other card already blocks this one - directly or through other cards - the link is refused, because neither card could then start.
Adding a link that is already there changes nothing.

If something goes wrong

"This card follows no tests that can run from a board. Link a saved request, suite, SQL case, cache check or UI track first."
"A card cannot link to itself."
"A link must be an absolute http(s) URL": paste the full address, starting with http:// or https://.
"You can view these cards but not change their links. Ask an organization admin for a role that can."
"Link cards to each other with a card link, not a record link.": use "Link a card" for another card.

/help/boards/bug-triage
/help/boards/cards-follow-the-work
/help/boards/board-timeline