Turn HappyFox support tickets into Linear bug reports

Every hour, review new HappyFox support tickets and turn genuine software bug reports into Linear issues so our support and engineering teams stay in sync. This runs on a schedule (cron); HappyFox tickets are pulled with a list operation rather than a live trigger, because HappyFox does not push ticket events to us.

Start by using HappyFox List Tickets to fetch tickets created or updated in roughly the last hour, meaning the window since the previous run. For each candidate, use HappyFox Get Ticket to read the full detail, including the original message, later updates, and any attachments. Skip any ticket that already carries the escalated tag, since it has been handled on an earlier run.

For each ticket, decide whether it describes an actual product bug. Treat it as a real bug when it reports error messages, crashes, steps to reproduce, data that is wrong, or behavior that clearly differs from how the product should work. Do not escalate how-to questions, account or billing questions, feature requests, or general feedback; leave those tickets untouched.

For each ticket that is a genuine bug, write a clean, self-contained bug report: a concise title, a short summary of the problem, the steps to reproduce, the expected versus actual behavior, the affected area of the product, the customer impact, and a reference back to the source HappyFox ticket (its display id such as #HFS00000001 and its ticket number). Before creating anything, check whether a matching Linear issue already exists for the same bug and, if so, reuse it instead of filing a duplicate.

Create the bug report with Linear Create Issue in the engineering team. Map the HappyFox ticket priority onto Linear's priority field: Urgent maps to Urgent, High maps to High, Medium or Normal maps to Normal, and Low maps to Low. Put the full bug report in the issue description using Markdown, and include a link back to the HappyFox ticket.

Once the Linear issue exists, post an internal note on the source HappyFox ticket with Add Staff Private Note, containing the new Linear issue's identifier and URL so support agents can follow the fix. This is an agent-only private note, so the customer never sees it.

Finally, use HappyFox Update Ticket Tags to add an escalated tag to the ticket. This tag is the guard that stops the same ticket from being escalated twice: on every run, skip tickets that already have it.

Keep the private note short and factual, never file more than one Linear issue for the same underlying bug, and if nothing on the current run is a real bug, simply do nothing. The result is that every genuine bug reported through HappyFox shows up as a tracked Linear issue, with a clear two-way link between the support ticket and the engineering work.