Ticketing Action

Ticketing actions execute when a supported trigger condition is met. That happens when an anomaly is detected, or when an anomaly changes to a status the trigger is filtered to. The action then creates a ticket, or updates the status of an existing one, in the connected ticketing integration.

Why Use a Ticketing Action

Use a Ticketing action when data quality findings should become work items in the tool the team already triages in. Common cases:

• Start the investigation where it will happen: A severe anomaly opens a ticket carrying its context, so triage begins in the tracker instead of in a channel message someone has to copy from.
• Keep the tracker in sync with the anomalies: Pair a Create Ticket Flow with an Update Ticket Status Flow on Anomaly Status Changed, so tickets move when the anomalies resolve.
• Make quality work visible: Tickets put data quality issues on the same board, with the same priorities and owners, as the rest of the team's work.

See Also