Create a Jira Bug issue from every bug report
Every submission on your bug report form opens a Bug issue in the product project, with severity already mapped to Jira Priority.
New submission on your "Report a bug" form
Create a Jira issue of type Bug in your product project, with the bug title as the summary, steps to reproduce in the description, and Priority set from the severity dropdown
One-directional. A submission triggers the action — nothing is written back into your form.
A bug report sitting in an inbox competes with everything else in that inbox. Filing it as a Jira issue the moment it arrives puts it where engineers already look, and carries the reporter's own severity judgement with it rather than losing that to a triage meeting.
It suits teams whose testers, support staff and customers all report through one public form while engineering works only from the board. The submission stays in formformform as the raw record; the issue carries the work.
Setting it up
- 1
Publish your bug report form and check that the severity dropdown uses the same words as your Jira priority scheme — Highest, High, Medium, Low.
- 2
In Zapier, point the formformform "New Submission" trigger at that form and pull in a sample report so every answer is available to map.
- 3
Add Jira's "Create Issue" action, select your product project, and set Issue Type to Bug.
- 4
Map the bug title to the Jira summary and keep it the only thing there, so the backlog stays scannable at a glance.
- 5
Build the description from several answers at once: the reproduction steps first, then expected against actual behaviour, then the browser and device string.
- 6
Map the severity answer to Priority. If the dropdown wording differs from your scheme, add a Zapier Formatter lookup step to translate it.
- 7
Add a static label such as "from-form" so reports filed this way can be filtered in or out during triage.
- 8
Submit a real test report, confirm the issue in Jira has a priority and a readable description, then switch the Zap on.
What maps where
Using the Bug Report Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Jira |
|---|---|
| Bug Title | Jira issue summary |
| Severity | Priority field on the issue |
| Steps to Reproduce | Description, under a reproduction heading |
| What Actually Happened? | Description, under an observed behaviour heading |
| Browser / Device | Description, or a custom environment field |
| Email Address | Custom reporter contact field |
Variations worth knowing
Add a Zapier filter so only the top severity creates an issue straight away, and send the rest through a second Zap into a triage project reviewed weekly. The board stays quiet and nothing is dropped.
The form asks where the bug occurs. Map that URL to a Jira component or label using a Formatter step that strips the domain and keeps the path, and the backlog groups itself by page.
If something isn't arriving
Jira matches Priority by exact name. A dropdown that says "Critical" when the scheme says "Highest" is dropped without an error. Rename the form options to match the scheme, or add a Formatter lookup step in Zapier.
Zapier joins mapped answers with no line breaks unless you put them there. Type each field on its own line in the description box and prefix it with a short heading before saving the action.
Frequently asked questions
Can the person who reported the bug see when it is fixed?
No. The connection runs one way — a submission creates the issue and nothing is written back to the form. The form does collect an email address, so send the update from your own mail tool once the issue reaches Done.
What happens when two testers report the same bug?
Two issues are created. Zapier cannot see what already exists in the project, so it never checks for duplicates. Most teams let both land and link them in Jira at triage, which takes less time than trying to prevent it.
How do screenshots reach the issue?
The bug report template asks for a screenshot or video link rather than the image itself. Map that URL into the description and engineers click through to whatever the reporter shared — a recording, an image host, a shared drive.
Related automations
- Create an assigned Jira task for every new hire's IT setup
A completed onboarding form creates an assigned setup Task in the IT project, with equipment and access needs listed in the description.
- File feature requests as Jira stories in your roadmap
Each feature request lands as a Story in your roadmap project, labelled so you can review the form-sourced ideas as a batch.
- Send beta feedback to Jira as triageable issues
Beta survey responses become labelled Task issues in the QA project, each tagged to the component the tester was using.
- Turn internal IT requests into prioritised Jira issues
Internal IT requests become prioritised issues on the team board, with the change type as the summary and a requested completion date.
- Turn support requests into Jira tasks
Contact-support submissions arrive as labelled Task issues in your support project, message intact and ready to assign.
- Add every RSVP to your confirmed guest list
Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free