Google Forms to Jira: Auto-create bug tickets from form submissions

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.

Additional information

What does this prompt do?

Watches your internal bug report Google Form for new submissions.
Creates a Jira issue in the project you choose, mapping the form answers to the title, description, environment, steps to reproduce, and reporter.
Sets the Jira priority based on the severity dropdown the reporter picked.
Posts a tidy confirmation in a Slack channel with the new Jira key, the reporter, and a deep link to the ticket.

What do I need to use this?

A Google account with access to the bug report form.
A Jira Cloud account with permission to create issues in the target project.
A Slack workspace and a channel where the team can see new bug tickets.

How can I customize it?

Pick which Jira project, issue type, and default labels every new bug lands under.
Change how form severity options map to Jira priority (for example, Critical to Highest, Minor to Low).
Choose which Slack channel gets the confirmation message and how it is formatted.

Frequently asked questions

Does this work with my existing bug report form?

Yes. Point it at any Google Form you already use. As long as the form has the standard fields (title, severity, steps to reproduce, environment, reporter email), the workflow will map them onto Jira. You can rename or add fields and update the mapping in one place.

Will it create duplicates if the form is submitted twice?

No. Each form response is processed once and produces a single Jira issue, with the response ID tracked so the same submission is not filed again.

Can I send the Slack confirmation to a private channel or a DM?

Yes. You can route the confirmation to any channel, private channel, or direct message that the connected Slack account can post to.

What if a reporter forgets to fill in a field?

The workflow falls back to sensible defaults (for example, Medium priority if severity is blank) and still creates the ticket so nothing gets lost.

Can I use this with Jira Server or Data Center?

This template is built for Jira Cloud. Jira Server and Data Center are not supported by the Jira integration.