Triggers (job header button) chains jobs by outcome: "when this job finishes with status X, run that job." Pick a target job and a status (Succeeded by default), click Add -- the target starts the moment the source job actually reaches that status, through the same queue a manual Run click uses. The dialog also lists incoming triggers -- other jobs already set up to start this one.

Triggers only fire off a whole job's real, completed outcome -- never from an ad-hoc single-step "Run Selected" test. Chaining several jobs together works fine, but nothing detects a cycle (Job A triggering Job B triggering Job A on the same status) -- avoid wiring one up.

See also: Glossary for related terms.