WORKFLOWS
A test result should lead somewhere.
Choose an event, filter what matters, and send the result to the next system. Keep the run link with the handoff.
- TRIGGERRun created
- CONDITIONOutcome is FAIL
- ACTIONCreate a Linear issue
FOLLOW A HANDOFF
Walk through the next action.
Choose an example. Built-in actions, engineer decisions and proposed extensions are labeled at each step.
Give a failed test an owner.
Filter a new run, create a Linear issue, and notify the people who need to inspect it.
- 1Built-in
A run is created
Start from the run-created trigger. The event provides the run and related unit, part, revision, batch, and procedure context.
- 2Built-in
Keep failed runs
Add a filter for the outcome and the procedure you want to monitor. Other runs stop at this branch.
- 3Built-in
Create a Linear issue
Use the Linear action to set a team, title, description, and optional assignee. Include the run link so the engineer can open its measurements.
- 4Built-in
Email the quality team
Use the email action and the issue URL returned by the previous step. The original run remains the source of the detailed measurement evidence.
Local walkthrough. Notifications, tickets, and hardware actions are simulated.
Keep the execution reviewable. Inspect the trigger, version, branch and per-node inputs and outputs. A failed action stays visible in history.
CONNECT YOUR TOOLS
Use the systems your team already opens.
Send messages, create issues, update stock or connect a custom API. Pass variables from the event and earlier steps into each action.
Workflows support created runs, units, parts, revisions and batches, plus scheduled and manual triggers. Alert routing and automated retest assignments in the examples are proposed extensions.
See triggers and actionsStart with one useful handoff.
Choose the event your team already responds to and connect it to a clear next action.
