Before
Responders likely looked up the affected brand’s ticketing system and manually selected the correct destination. They then reformatted and copied the incident details, added context, and returned the resulting ticket reference to the calling workflow.
How it works
- Receive the brand and response-ticket details from the parent workflow.
- Resolve the brand’s destination, normalize priority and ticket content, and select the matching ticket format.
- Open or replay the ticket-creation response for the selected branch and return the ticket reference and brand.
Workflow details
- Receive ticket details: A parent workflow supplies the affected brand, ticket title, description, and optional priority, labels, source, and reference.
- Resolve the destination: The workflow looks up the brand’s configured ITSM route, applies a default route for unknown brands, and selects the appropriate ticket format.
- Prepare the response ticket: It maps severity values, adds standard labels, preserves description paragraphs, and appends the originating workflow and reference to the ticket content.
- Return the handoff result: The selected Jira Cloud, Jira Data Center, or ServiceNow branch returns the target system, brand, and ticket key or incident number, including a concise error result when creation is unsuccessful. The supplied demonstration responses are synthetic and replayed locally.
What changed
A single workflow interface now handles brand-based routing across three ticketing branches. Destination selection, priority mapping, content formatting, standard labeling, and result extraction happen automatically, while the caller receives one consistent response containing the ticket reference or an explicit creation error.
Work removed
Looking up the brand’s ITSM destination, choosing the correct ticketing branch, reformatting descriptions and priorities, copying labels and source references, and manually returning the ticket identifier.
Expected outcome
At least three recurring manual actions per request—destination lookup, ticket reformatting, and result handoff—are replaced by a consistent automated routing process.
