create-ticket

Creating trackable tickets from chats requires submitting a title, description, priority, and assignee to the /api/tickets endpoint. This process captures essential context and establishes a persistent work item with a clear lifecycle and ownership.

Creating a ticket via the API requires a title, description, priority, and assignee as mandatory fields. You can also optionally include goal_id and project_id to link the ticket to broader projects and goals for dashboard reporting.

Yes, you can link ad-hoc conversation tickets to existing projects and goals by passing the optional goal_id and project_id fields when posting to the /api/tickets endpoint. This integrates the ticket into dashboards and broader project workflows.

You need to convert a conversation into a persistent ticket when ongoing discussions involve recurring topics, incidents, or multi-person projects that require assigned ownership and clear lifecycle tracking to prevent miscommunication and lost context.

Yes, this ticketing workflow supports priority and assignment management by requiring priority and assignee fields upon creation. This ensures every persistent ticket generated from a chat has clear ownership and urgency levels for dashboard tracking.