Jira
Jira ticket creation is live for drift-budget breaches: connect a site with an email + API token, set a target project key, and Vibgrate opens a Jira issue automatically the moment a budget crosses its critical threshold.
What's live today
Jira connections authenticate via HTTP Basic auth (an Atlassian account email + API token) against a Jira Cloud site, targeting a single project key. When a drift budget breaches its critical threshold, Vibgrate creates a Jira issue (summary, priority mapped from the breach, and a description with a link back into Vibgrate) on every enabled Jira connection in the workspace. Use the connection's Test button to create a one-off connectivity-check issue.
What's still coming
Ticket creation from approval_requested events, per-connection event-type selection (today it's every breach → every enabled connection), and OAuth-based site install (today it's an API token) are not yet available.