Collect product feedback in a review queue
Feature requests land in the Product Feedback project as tagged tasks, ready for the weekly triage pass.
New submission on your feedback or feature request form
Create a task in the Product Feedback project, tagged by theme, with the full comment in the description for the product team to review
One-directional. A submission triggers the action — nothing is written back into your form.
Feedback is easy to collect and easy to lose. It arrives in support tickets, sales calls and a channel nobody has read since March, and the pattern only becomes visible once someone sits down and reads six months of it at once. A queue fixes that by making each request a task on the day it arrives.
Tagging by theme is what makes the queue worth keeping. A dozen separate requests for the same missing export turn into one tag with a dozen tasks on it, which is an argument a product team can take into a roadmap meeting.
Setting it up
- 1
Create the Product Feedback project with sections for New, Under Review and Planned, and set up Asana tags for the themes you already know recur.
- 2
Publish the feature request form. Keep Feature Title short and required, because it becomes the task name everyone scans.
- 3
Set up the Zap with formformform's New Submission trigger, watching the feedback form.
- 4
Add Asana's Create Task action, set Project to Product Feedback and Section to New.
- 5
Map Feature Title to the task name, then build the description from What problem does this solve? and What would you like to see?, so the reasoning survives and not just the ask.
- 6
Add a theme single-select to the form and map it to the Asana Tags field, or use Zapier Paths to apply a fixed tag per answer.
- 7
Map How important is this to you? to a priority custom field, so the weekly pass can sort the queue by it.
- 8
Test one request, check the tag applied and the description is readable, then switch the Zap on.
What maps where
Using the Feature Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Asana |
|---|---|
| Feature Title | Task name in the Product Feedback project |
| What problem does this solve? | Task description, first paragraph |
| What would you like to see? | Task description, under the problem |
| How important is this to you? | Priority custom field |
| Who else would benefit? | Task description, as evidence of demand |
| Email Address | Requester custom field, so you can close the loop later |
Variations worth knowing
How are you working around it today? is the field that separates an annoyance from a blocker. Map it to its own custom field and sort the queue on it. Anyone describing manual work every week is describing a gap worth costing properly.
Add a filter for requests marked as most important and give them a second Asana action that also creates a task in the owning squad's project. The review queue keeps the full record while the urgent items reach an engineer the same day.
If something isn't arriving
The Asana action creates a tag when it cannot find an exact match, so a trailing space or different capitalisation makes a duplicate. Pass fixed values from a path rather than the raw answer, then tidy up any stray tags already in Asana.
Nothing deduplicates on its own. Run a Zapier Find Task step against the Product Feedback project first and, when a close match exists, add an Asana comment to that task instead of creating another. Merging by hand during the weekly pass works too.
Frequently asked questions
Does the person who requested the feature find out if we build it?
Not automatically. The connection only pushes submissions into Asana, and nothing travels the other way. Map the email address into a custom field, then send the update from Asana or your mailing tool when the task reaches your Shipped section.
Should feedback and bug reports go to the same board?
Separate them. A bug has a defect to fix and a bounded lifespan, while a feature request is a roadmap candidate that may sit for a year. Two forms and two Zaps keep the triage conversations distinct, even when one team runs both.
Can we accept anonymous feedback and still file it?
Yes. Make the name and email fields optional in the form. The Zap runs regardless and creates the task with those custom fields blank. You give up the ability to follow up, which is the trade some teams make for more candid answers.
Related automations
- File client requests as project tasks
New intake requests arrive as tasks in Client Requests, with the stated scope and deadline already filled in.
- Move job applications into a hiring pipeline
Applicants appear as tasks in the Recruiting project, sorted into the section for the role they applied for.
- Track event sign-ups as follow-up tasks
Every registration becomes a task assigned to the event host, carrying dietary notes and guest numbers.
- Turn bug reports into triage tasks
Each bug report lands in the Bugs project's Triage section with reproduction steps already in the description.
- Turn wholesale orders into shipping tasks
Orders arrive as tasks in the Fulfillment project, assigned to operations with a due date for dispatch.
- 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