Turn Google Form bug reports into Jira issues

By General Input

Every time someone submits your internal bug report form, file a Jira issue in the right project and post a confirmation in Slack.

Integrations

  • Google Forms
  • Jira
  • Slack

Type

Deterministic Code

Categories

  • Engineering
  • Product

Build a code workflow that turns internal bug report submissions in Google Forms into Jira issues and posts a confirmation in Slack.

Trigger: poll Google Forms for a new_response on our internal bug report form. The form has these fields: a short Title, a Severity dropdown (Critical / High / Medium / Low / Minor), a Steps to reproduce long-text, an Environment field (browser/OS/app version), and the Reporter email (collected via the form).

Step 1: Use Google Forms Get Response to fetch the full response by ID so we have all answers and metadata.

Step 2: Build the Jira description deterministically from the form answers as a single ADF block with these sections in order: a one-line summary line referencing the reporter, then headings for Steps to reproduce, Environment, and Reporter, with the matching answers underneath. No LLM step. Pure mapping.

Step 3: Call Jira Create Issue in a fixed project (make the project key, issue type, and default labels configurable). The Jira summary is the form Title field. Map the Severity dropdown to Jira priority: Critical -> Highest, High -> High, Medium -> Medium, Low -> Low, Minor -> Lowest. Default to Medium if severity is missing or unrecognized. Set the reporter email as a custom field or include it in the description if it cannot be set as the Jira reporter.

Step 4: Use Slack Send a Message to post into a configurable channel. The message should include the new Jira issue key, a deep link to the issue (https://<your-domain>.atlassian.net/browse/<KEY>), the reporter email, the title, and the priority. Format it cleanly so the channel can scan it at a glance.

Make the Jira project key, issue type, severity-to-priority mapping, and Slack channel exposed as workflow config so they can be edited without changing the flow. No judgement steps anywhere. Every node is a known integration call.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes