Feedback routing rules decide where each user acceptance testing (UAT) submission goes after a tester sends it: which tracker, which backlog, which named owner. Good rules use a few reliable fields (product area, severity, environment, report completeness), are checked in a fixed order, and always end in a fallback owner. This guide shows how to build them, how to keep duplicate and incomplete reports out of your backlog, and how they work with Jira and Azure DevOps.
TL;DR
- A routing rule is an “if this, then send it there” statement. It sends a UAT submission to an owner based on category, severity, product area or account tier.
- Route on a small set of structured fields, not on keywords in free text. Vocabulary changes, structure holds.
- Number your rules, check them in order, let the first match win, and name a fallback owner for everything that matches nothing.
- Validate the minimum report standard before routing, and catch duplicates at capture so they never reach the backlog.
- Review misrouted items every cycle and adjust the rules. Rules that nobody revisits drift out of date.
Table of Contents
- What feedback routing rules are and what they fix
- Which fields to route on
- How to write and order the rules
- Keep incomplete and duplicate reports out of the backlog
- From submission to retest: the full flow
- Routing rules in Jira and Azure DevOps
- Monitor and improve your rules
- Perspective: route at capture, not after
- Put it into practice with Wezard
- FAQ
- Sources
What feedback routing rules are and what they fix
A routing rule answers one question: when a submission arrives, who gets it? In UAT, the answer might be an engineering tracker, a product backlog or a specific team owner, chosen by criteria such as category, severity, product area or account tier, as a glossary entry on feedback routing describes. Without rules, enterprise-critical bugs can sit in a general queue while minor notes ping engineers directly.
The problem is bigger in UAT than in most testing. UAT challenges include feedback that is inconsistent, unclear or conflicting, which makes it hard to see the real issues and rank improvements. Business users are not testers by trade. They describe the same defect in five different ways, attach nothing, or report a change request as a bug. Routing rules are the first line of defense, because they turn a pile of messy submissions into work that lands on the right desk.
Routing is one of three parts of triage. Classification puts an item into a category. Prioritization scores its urgency. Routing delivers it to an owner. If you want the full picture of the other two, our guide on UAT bug triage covers sorting, ranking and closing feedback, and the defect triage process article breaks down outcomes and decision factors.
Accurate routing also matters beyond the test cycle. Feedback that reaches someone who can act on it is what makes feedback programs pay off, a point explored in this piece on customer feedback and revenue growth.
Which fields to route on
The quality of a rule depends on the field behind it. A rule that reads “if the text contains ‘invoice’” is fragile. A rule that reads “if product area equals Billing” is stable. Pick fields testers can fill in quickly, or that the tool captures automatically.
A UAT defect triage guide lists the information worth collecting for routing and prioritization:
- Product area or component
- Environment and build
- Reproducibility and exact steps
- Expected and actual result
- Business impact, severity and priority
- Evidence such as screenshots or recordings
- Linked test artifacts
- Reporter contact and availability
The same guide names the roles that make the decisions: a triage lead, a business or product owner, a development representative and a QA or test lead. Your rules should map onto those roles, so every rule ends with a person or a group, never with “the team”.
Keep severity and priority apart
Severity describes the technical or user impact. Priority is the business decision about what to fix first. A bug report triage template recommends recording both during triage. This matters for routing because the two fields send items to different places. A high-severity defect in a rarely used screen may be routed to the owning developer with normal priority. A cosmetic flaw on the checkout page of a launch may be routed urgently because the business says so.
A starter routing table
Use this as a template and replace the owners with your own.
| Order | If the submission is… | Route to | Fallback |
|---|---|---|---|
| 1 | Missing minimum report fields | Back to the reporter for details | Triage lead |
| 2 | A known issue already published | Linked to the existing item | Triage lead |
| 3 | High severity, any product area | Engineering lead, same-day review | QA lead |
| 4 | Product area equals a named module | That module’s owner | QA lead |
| 5 | Looks like a change request | Product owner backlog | Business analyst |
| 6 | Matches nothing | Triage lead, reviewed daily | Project manager |
How to write and order the rules
The structure matters more than the number of rules. Teams that write thirty rules in the first week usually spend the second week untangling them. Start with five or six.
- Agree on definitions first. Severity definitions and the triage process should be settled before the first defect is logged in a UAT cycle, not improvised once people disagree. Write down what Critical, High, Medium and Low mean in business terms.
- Publish known issues. The same guide advises sharing the known-issues list from earlier test phases before UAT starts, so business testers do not rediscover and re-report bugs the team already knows about. A known-issues rule is often the cheapest way to cut noise.
- Number the rules and check them in order. The first match wins. This removes arguments about which of two matching rules applies, because the order decides.
- Name an owner and a fallback for every rule. An owner on vacation should not stall a defect. The fallback is a named person, not a mailbox.
- Put exceptions above general rules. A rule for a regulated workflow or a key account goes before the generic product-area rule, or it will never fire.
- End with a catch-all. Something always arrives that no rule predicted. Send it to the triage lead and review that bucket often. If it fills up, you have found a missing rule.
When two groups could own an item, choose the group that would do most of the work. Whoever does the bulk of the fix should hold the ticket, and others can be linked or notified.
Route on structure, not on keywords
Routing directly on words in the report breaks the moment testers change how they describe things. One tester writes “can’t pay”, another writes “checkout spinner”, a third writes “card error”. Classify the item into a stable category first, then route on the category. That keeps your rule set small and lets it survive changes in language. It is also why guided submission, where the tester picks the area and type from a short list, beats a blank text box.
Keep incomplete and duplicate reports out of the backlog
A routing rule that works perfectly still fails if the item it routes is unusable. Two checks belong before any routing happens.
Completeness. A minimum report standard should be validated first. If required information is missing, the item goes back to the reporter with a specific question, rather than being forwarded as an incomplete ticket, as the bug report triage template recommends. Define the minimum in one line: where, what you did, what you expected, what happened, and evidence. Our guide to submitting clear bug reports to developers is a handy page to hand to testers, and paste-ready bug reproduction steps shows what good steps look like.
Duplicates. In a UAT cycle with dozens of business users, many people hit the same defect on the same day. If each report becomes a ticket, the triage lead spends the first hour of every morning merging them. Catching duplicates at capture is far cheaper than merging them later. We cover this in stopping duplicate tickets with in-app bug reporting and preventing duplicate Jira tickets at capture.
A useful order for these checks: completeness first, duplicate check second, routing third. Routing a duplicate to an owner just creates a second person working on the same problem.
From submission to retest: the full flow
Routing is one step in a chain. Here is the path a feedback item takes in a well-run UAT cycle.
- Submission. The tester records or describes the issue, with evidence attached.
- Normalization. The report becomes a consistent structure: tester, build, page, message.
- Classification. The item is categorized, for example as a critical bug, feature request, UX improvement or noise.
- Routing. Rules send it to its owner.
- Assignment and fix. The owner accepts it, or bounces it with a reason.
- Retest. The original tester confirms the fix in the next build.
- Closure. The item is closed, and the tester is told.
An automation template for UAT feedback shows this pattern in practice: feedback is normalized, classified with a confidence score, then routed, with critical bugs going to Jira plus an engineering alert, feature requests to a roadmap, UX improvements to design tracking, and noise archived but still traceable. The point to borrow is the last one: nothing is deleted, even when it is not acted on.
Also close the loop. Testers who never hear back stop reporting. Tell the reporter where their item went and what happened. Our walkthrough on tracking software feedback status in Jira shows one way to do it.
Routing rules in Jira and Azure DevOps
Most teams implement rules inside the tracker they already use.
Jira. You can define UAT-specific statuses and use automation to assign issues, notify or escalate stakeholders, and create approval issues when tests pass, according to a Jira UAT workflow guide. The same guide suggests statuses such as Ready for UAT, In UAT, UAT Failed, UAT Passed, UAT Approved and Closed, with entry and exit criteria. Each status change is a routing opportunity: UAT Failed can assign back to the developer, UAT Passed can notify the approver. We walk through a no-plugin build in our Jira UAT workflow guide, and intake forms as task templates can remove the delay between a report arriving and someone looking at it.
Azure DevOps. Area paths and iteration paths are the natural fields to route on, and our Azure DevOps bug reporting best practices page covers how to structure them. If your organization uses both Jira and Azure DevOps, synchronization can be one-way or two-way, and you can filter which work items sync or set destination statuses automatically, as documented for Jira and Azure DevOps sync flows. Decide which tool is the source of truth for each type of item before you turn sync on, or the same defect will bounce between systems.
Routing across several connected tools is also where workflow automation platforms come in. Teams exploring this often look at AI agent workflow automation to connect approvals, triggers and multiple systems, but the rules themselves still need the clear owners and fallbacks described above.
Monitor and improve your rules
A rule set is a living document. Review it on a schedule, and look at the evidence.
- Misroute rate. Count how many items were reassigned after routing. A rule that is reassigned often is wrong or too vague.
- Catch-all volume. If the fallback bucket holds more than a handful of items per cycle, add a rule for the pattern that keeps landing there.
- Time to first touch. Measure the gap between submission and the owner’s first action, per rule. A slow rule often points at an owner who is overloaded or unaware.
- Bounce-backs for missing details. If one product area keeps returning incomplete reports, change the submission form for that area.
- Misses, not just hits. Look at what automation failed to route correctly, not only at what it caught. Successes are easy to count and tell you little.
- Human review for the ambiguous middle. Where a classification is uncertain, a person should decide. Keep the automated path narrow and clear.
Run this review at the end of each UAT cycle and after any change in team ownership. Treat each change as a version: note the date, the reason and who approved it, so the next cycle starts from a known state. The UAT change management process covers how to document those changes without slowing the release.
Perspective: route at capture, not after
We build Wezard around one belief: the best routing rule is the one you never have to apply by hand. Most UAT noise is created in the first minute, when a business user types a vague sentence into a form and moves on.
That is why Wezard records the screen, transcribes the issue in real time and uses AI to detect duplicate tickets before they reach your Jira or Azure DevOps backlog. The tester talks through the problem, the ticket arrives with the evidence already attached, and the duplicate check happens before a triage lead ever sees it. Our own figures point to a reduction in duplicate noise of up to 40% compared with manual processes or basic feedback tools.
Rules still matter. Owners, fallbacks and severity definitions are decisions only your team can make. But when intake is clean, those rules can stay short, and the people applying them spend their time on real defects instead of sorting.
Marketing
Put it into practice with Wezard
If you want routing rules to start from clean, enriched tickets, Wezard is built for exactly that step. Testers submit by voice or video with guided prompts, screenshots and files can be attached, and duplicates are flagged before the ticket is created. Tickets then go straight into Jira, Azure DevOps or ServiceNow. Security is enterprise grade, with SOC 2 certification and SSO.
Plans are published on our pricing page: Starter at $25 per month, Team at $70 per month and Business at $160 per month, with Enterprise available on request. You can see how the feedback workflow fits your cycle on the UAT testing feedback tool page, or read how the Azure DevOps feedback integration works.
FAQ
What is the difference between triage and routing?
Triage is the whole process of classifying, prioritizing and assigning feedback. Routing is the last part: delivering the classified item to the right owner or tracker. You can have good routing only if classification comes first.
How many routing rules should a UAT team start with?
Start with five or six: a completeness check, a known-issue check, a high-severity rule, a product-area rule, a change-request rule and a catch-all. Add a new rule only when you see the same misrouted pattern repeat across a cycle.
Who should own the routing rules?
The triage lead should own the rule set, with input from the QA lead, the business or product owner and a development representative. One named owner keeps the order of rules consistent, and the others agree on severity definitions before testing begins.
Should we route by keywords in the report?
Use keywords sparingly. Testers describe the same problem in different words, so keyword rules break easily. Classify the item into a stable category or product area first, then route on that field.
How do we stop duplicates from reaching the backlog?
Publish known issues before testing starts and check for duplicates at capture, before a ticket is created. Doing it at the source is cheaper than merging tickets afterward, and it keeps owners from working on the same defect twice.
Sources
- What is feedback routing?
- User Acceptance Testing (UAT), GeeksforGeeks
- UAT Defect Triage: Prioritize and Resolve Fast
- Bug Report Triage SOP Template
- Running UAT on a Multi-Stakeholder Program
- Triage product UAT feedback workflow template
- UAT Workflow in Jira
- How to Sync Azure DevOps and Jira
- Customer feedback and revenue growth
- Enterprise AI delivery


