IT ticket intake and triage workflow with Jira routing
Build an employee-facing IT help desk intake workflow. The goal: a person opens a web form, describes their problem and picks a category and severity, and the workflow files a ticket routed to the right team and announces it in a team chat channel. Trigger it with two HTTP routes, both gated to space members so requests carry a signed-in email: A GET route serving a branded web form (name, email prefilled from the signed-in account but editable, a title, a description, a required category, and a severity). The page renders immediately, POSTs its data as JSON to the submit endpoint, and shows the created ticket (or an inline error). A POST API route that receives the form submission, validates and length-checks the body, rejects oversized or invalid input with a 400, and derives routing deterministically (no AI): team from the chosen category, and a priority mapped from severity (Critical→P1 down to Low→P4). Then create the ticket in an issue tracker — use Jira, or your team's tracker — mapping the title, description, priority, and category/team into the issue. Return the created issue key and a link back to the form. Make this step reliable: retry transient failures with backoff, and if creation ultimately fails, write the ticket to a durable dead-letter store so nothing is ever lost and give the submitter a graceful "saved, filing shortly" reference. Finally, post the new ticket to a chat channel — use Slack, or your team's chat tool — with the issue key, team, priority, and a one-line summary; and when a ticket was dead-lettered, post an alert instead so a human can file it manually. Style the form nicely and keep the whole flow rule-based — no model/AI connector needed. Tools used: Jira, Slack
What this prompt builds
This workflow centralizes IT support requests through a single web form that captures issue details, validates input, routes tickets to the correct team based on category, creates Jira issues with mapped priorities, and posts notifications to Slack. It includes dead-letter handling to ensure no ticket is lost if Jira is unavailable. IT teams receive complete, pre-routed tickets while employees get immediate confirmation and tracking links.
The problem
IT requests arrive scattered across Slack, email, and hallway conversations, often missing critical details or context. Tickets land on the wrong team, forcing manual triage, and some requests never get logged at all, leaving employees without resolution or visibility. IT teams waste time chasing information and routing misplaced tickets instead of solving problems.
Solution and impact
The workflow routes requests to the correct team automatically based on category, files complete Jira tickets with mapped priorities, and posts confirmations to Slack with tracking links. Dead-letter handling ensures no ticket is lost even when Jira is unavailable. IT teams skip manual triage and receive structured, actionable tickets while employees get instant confirmation and a reference to track their request.