--- title: "Bug reports to a Trello triage list" description: "Send each bug report form submission to Trello as a card on your \"Inbox\" list, with reproduction steps in the description and a red label on severe ones." url: "https://www.formformform.com/automations/trello-bug-reports-to-triage" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![Trello logo](/logos/integrations/trello.svg) # Create a triage card for every bug report Reported bugs land as cards on your "Inbox" list, with reproduction steps in the description and a red label on severe ones. When this happens New submission on your "Report a problem" form Do this Create a card on the "Inbox" list with the issue summary as the title, full details in the description, and a red "Urgent" label when the reported severity is high One-directional. A submission triggers the action — nothing is written back into your form. Bug reports arrive in whatever shape the reporter felt like typing. A form fixes the shape; this flow puts each report on the "Inbox" list of your triage board as a card titled with the reporter's own one-line summary. Product and QA teams lean on it during a release week, when reports come in faster than anyone can copy them across. Reproduction steps, browser and the affected URL all land in the description, so whoever is triaging can add a member and move the card to "In progress" without going back to ask. ## Setting it up 1. 1 Publish the bug report form and submit one real bug, filling in Severity and Steps to Reproduce so Zapier has a complete sample to map from. 2. 2 Set the formformform "New Submission" trigger to that form, then load the sample and check the severity value comes through as text you can match on. 3. 3 Add Trello's "Create Card" action pointed at your triage board, with the list set to "Inbox" so nothing lands mid-workflow. 4. 4 Map Bug Title into the card's Name field on its own — it is already written as a summary, so nothing needs appending. 5. 5 Assemble the Description from Steps to Reproduce and What Actually Happened?, each under its own short heading. Trello renders markdown in descriptions, so ## headings and blank lines survive. 6. 6 Add Browser / Device and URL Where the Bug Occurs at the foot of the description, where the engineer picking the card up will look for them. 7. 7 Create a red "Urgent" label on the board, then add a Zapier Paths step that only applies it when Severity comes through as high. 8. 8 Test twice — once with a high-severity report and once with a low one — and confirm the label appears on the first card and not the second before turning the Zap on. ## What maps where Using the [Bug Report Form](https://www.formformform.com/templates/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 Trello Bug Title Card name on the "Inbox" list Severity Decides whether the red "Urgent" label is applied Steps to Reproduce Card description, under a "Steps" heading What Actually Happened? Card description, under an "Actual result" heading Browser / Device Foot of the card description URL Where the Bug Occurs Foot of the card description ## Variations worth knowing Keep severe reports off the general inbox Use Paths so high-severity reports create their card directly on "In progress" and everything else lands on "Inbox". The board then shows at a glance whether anything needs attention today, without a person reading through the whole triage column first. Keep the reporter reachable from the card Map Your Name and Email Address into the top of the description. When an engineer needs one more detail to reproduce something, the address is on the card rather than three tabs away in the responses table. ## If something isn't arriving The "Urgent" label lands on every card, including minor bugs A Paths or Filter step placed after the Create Card action does not stop the card being made. Move the branch above the Trello step, and match the exact severity option text rather than testing whether the field merely has a value. The description arrives as one unbroken paragraph Zapier collapses the layout unless you add the line breaks yourself. Put each mapped field on its own line inside the Description box, with a blank line between blocks, and Trello will render the headings and spacing as written. ## Frequently asked questions Is a Trello board enough, or do we need a real bug tracker? For a small team triaging a handful of reports a week, a board with "Inbox", "In progress" and "Done" is usually enough. Teams tracking regressions across releases outgrow it, at which point the same form can feed the tracker instead. Can the person who reported the bug see the card move? No. Nothing is sent back to the form or the reporter — the flow only creates the card. If you want to close the loop, collect the reporter's email on the form and send an update from your own mail tool. What if the same bug gets reported five times? You get five cards. Most teams triage them into one and archive the rest, which also tells you how many people hit the issue. A Zapier "Find Card" search step before the action can catch obvious repeats by title. ## Related automations - [Add every RSVP to your confirmed guest list](https://www.formformform.com/automations/trello-rsvps-to-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. - [Drop each job application onto your hiring board](https://www.formformform.com/automations/trello-applicants-into-hiring-pipeline) Every application becomes a card on the "Applied" list, labelled with the role and carrying the cover letter in its description. - [Send feature requests to your product backlog](https://www.formformform.com/automations/trello-feature-requests-into-backlog) Feature requests become cards on your "Ideas" list, labelled by how badly the person asking needs them. - [Turn custom orders into dated fulfilment cards](https://www.formformform.com/automations/trello-orders-to-fulfilment-list) Custom orders arrive as cards on your "To fulfil" list, titled with the item and carrying the customer's date as the due date. - [Turn website enquiries into cards on your sales board](https://www.formformform.com/automations/trello-leads-to-sales-board) Each contact form submission opens a labelled card on your 'New leads' list, ready for a rep to pick up. - [Add new sales leads to your pipeline board](https://www.formformform.com/automations/monday-sales-enquiries-to-pipeline) Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work. - [All Trello integration details →](https://www.formformform.com/integrations/trello) - [Start from the Bug Report Form →](https://www.formformform.com/templates/bug-report-form) - [Browse every automation →](https://www.formformform.com/automations) ## 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](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=trello-bug-reports-to-triage)