Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.draftt.io/llms.txt

Use this file to discover all available pages before exploring further.

Draftt integrates with your existing ticketing system to turn governance findings into actionable tickets. Each ticket includes the resource context, ownership, and remediation guidance so engineers have what they need without leaving their existing workflow. For setup instructions, see Ticketing.

​
Creating Tickets

Tickets can be created manually from any finding in Draftt, or configured to be created automatically based on severity thresholds and routing rules. Manual creation is the default. Each ticket includes:
  • What is affected: Resource name, type, cloud account, and region
  • What the finding is: Policy name and the specific condition that triggered it
  • Who owns it: Resolved owner and team
  • How to fix it: Remediation guidance specific to the resource type
  • Link to Draftt: Deep link back to the full finding for complete context

​
Ticket Routing

Configure routing rules in Settings > Integrations > [Your Ticketing Platform] > Routing to control where tickets are created and how they are assigned:
  • Default project: Where tickets go when no specific routing rule matches
  • Team routing: Map Draftt team labels to ticketing projects or boards
  • Severity mapping: Map Draftt criticality levels to your platform’s priority scheme
  • Issue type: Which issue type Draftt creates (Bug, Task, Incident, etc.)

​
Ticket Status

Draftt syncs ticket status directly from your ticketing platform. Status labels reflect whatever your platform returns. Draftt does not impose its own lifecycle on top of your workflow.

​
Deduplication

Draftt does not create a new ticket if an open ticket already exists for the same finding on the same resource.

​
Next Steps