Use feedback tools when something is broken, confusing, missing, or worth improving.
The fastest path is to open the quick feedback panel from the app shell, then move into Feedback Hub if you need search, voting, comments, or status follow-up.
Quick facts
Start here
- Quick feedback picks up route context so the team has more detail without extra typing.
- A strong bug report includes what happened, what you expected, and how to reproduce it.
- Before you create a new feature request, search for an existing one and upvote it if it already matches.
- Managers can use comments and vote patterns to decide what needs follow-up first.
Step 1: Send quick feedback from the app shell
Use the fast panel when the issue just happened
Open the feedback panel from the app shell.
Send the feedback while the route, page state, and problem details are still fresh.
- 1 Check existing submissions first so you do not create a duplicate issue.
- 2 Describe what happened, what you expected, and enough detail to reproduce it.
- 3 Open Feedback Hub when you need the full search, voting, and comment view.
Step 2: Use Feedback Hub to search, upvote, and comment
Search first before opening a duplicate issue
Open Feedback Hub.
Search and filter first. If the issue already exists, upvote it and add a helpful comment instead of creating a duplicate.
- 1 Search first before you open a duplicate bug or feature request.
- 2 Use the grouped submission list to find the matching report.
- 3 Open the detail panel to read the full report, vote, and review the discussion.
Step 3: Close the loop with clear follow-up
- Use comments to share extra detail, screenshots, or a better reproduction path.
- Managers should watch for repeated themes, not only single loud reports.
- When an issue is resolved or clarified, update the record so the next person can see the outcome.