Feedback status automations keep customers informed as their requests move through your backlog. When a connected work item reaches a mapped status in Craft.io, the feedback item updates automatically and the submitter is notified - so the full delivery loop, from customer request through to completion, runs without anyone having to track it manually.
Feedback status automations are available on Pro plans and above. If you do not see the Feedback Status Mapping section in your Status Mapping settings, reach out to your Customer Success Manager.
How feedback status automation works
You define a mapping: when a work item reaches a specific status, any feedback item connected to it moves to a corresponding feedback status.
When it fires: the rule fires when all work items connected to a feedback item share the same mapped status. If only one of several connected work items has reached the mapped status, the automation holds until the rest catch up. A feedback item is never marked complete when only part of the work is done
What triggers it: a status change made directly in Craft.io, or a status update from a connected dev tool (Jira, Azure DevOps, or Linear). When a dev ticket closes and syncs to Craft.io, the automation fires just as it would for a manual update.
This requires status mapping from your dev tool to be set up, so that dev tool changes update the Craft.io status first
Direction: one way only. A work item status change updates the connected feedback item, but changing a feedback status never affects the work item
How to set up a status mapping rule
Follow these steps:
Go to Workspace Settings > Statuses > Status Mapping
Scroll to the Craft.io - Feedback Status Mapping section
Click + Add Rule
Under All Connected Work Items Statuses, select the work item status. Under Feedback Item Status, select the feedback status it should trigger
Save the rule
You can add as many rules as you need - for example, mapping Dev in Progress to In Progress and GTM Launch to Released.
Map the transitions that matter to the person who submitted the request, typically when work begins and when it is complete. Not every status needs a feedback update.
When saving a rule, you have the option to Apply rules to existing items. This immediately updates all feedback items already connected to work items in the mapped status. Use this when setting up the feature for the first time to bring your existing feedback statuses in line with where the connected work actually is.
What the submitter sees
When a feedback item's status updates through the automation, the submitter receives an email notification letting them know the status of their request has changed. They do not need to follow up, and you do not need to remember to tell them.
For teams using the feedback portal as a customer-facing channel, this gives submitters a live view of where their requests stand - not just a submission confirmation.
What comes next?
Connect and promote feedback to the backlog - link feedback items to work items to enable status automation
Core concepts - feedback items, companies, submitters, and statuses - understand how feedback statuses work
Setting up a feedback portal - configure your portal from scratch
Need more guidance? 🙋 Our LIVE support team (at the bottom right corner of your screen) replies to ANY question!


