Ask the reviewer to confirm the fix
When a fix is ready, the person who reported the problem, or another reviewer you choose, checks it on the page. They confirm the fix or say it still needs work, and the thread records who decided and when.
How it works
Three steps on a thread you already have. Replies, priority and search keep working throughout.
- Request verificationIn the app, choose Ready to verify in a thread’s status menu; in the toolbar, choose Request verification. Add a short fix summary and an optional fix link, then choose the reviewer. The original author is suggested while they still have access.
- Ready to verifyThe thread shows Ready to verify in the app, on the page and in the toolbar inbox, and still counts as open. The reviewer gets an email under their usual notification settings.
- Confirm fix or Still needs workThe reviewer checks the page. Confirm fix marks the thread done with their name and the time. Still needs work moves it to In progress for the next attempt.
Who can decide
Only the reviewer you asked can confirm the fix, or an admin who says they are deciding for them.
| Action | Who | Result |
|---|---|---|
| Request verification | A project member who can see the thread | Ready to verify. The thread counts as open, even if it was done. |
| Confirm fix | The requested reviewer | Done, with the reviewer’s name and the time. |
| Still needs work | The requested reviewer | In progress, marked Still needs work. The next check is a new request. |
| Confirm fix as admin, Still needs work as admin | A workspace admin who is not the requester or the reviewer | The same result, labeled as an admin override for the reviewer. |
| Cancel request | The requester or an admin | Back to Open or In progress, where it was before the request. In the app’s status menu, choose which. |
| Done without verification | Anyone who can already mark the thread done | Done without reviewer confirmation. |
| Reopen | Anyone who can already reopen the thread | Open. An earlier confirmation is kept as history only. |
Guests answer as themselves
When the reviewer is the guest who left the feedback, they answer with the same visitor identity, in the browser they commented from, while anyone with the link can still comment on the project. No account or email check is needed, and other guests cannot answer for them.
No one else steps in
If the original author is gone or has lost access, choose another member who can see the thread. The requester can never be the reviewer.
Done is not the same as confirmed
A thread can be done without anyone checking the fix. Only a reviewer’s decision counts as confirmation.
Done without verification
Marking threads done, one at a time or with bulk triage, is ordinary completion, never a reviewer’s confirmation. A thread that was Ready to verify shows Done without reviewer confirmation.
Connected issue trackers
With two-way status sync on, closing the issue in a connected service marks the thread done without confirmation. Ready to verify shows there as open.
AI agents
An agent can request or cancel a check after you approve it. It cannot confirm a fix.
Reopen
Reopening a confirmed thread makes the earlier confirmation history. A new check starts a new request.
Copy issue, the MCP connector and connected services include the outcome, with the name and time of the decision, beside the usual open or done status.
Fix links
Point the reviewer at the fixed page. A short summary says what changed.
- The fixed page on one of the project’s addresses, such as staging
- A preview deployment or a pull request, over HTTPS
- A short plain-text summary of what changed
Links to other sites cannot carry a query string, a fragment or credentials, and links to the project’s addresses can carry only the page state the project allows. uier never fetches or embeds a fix link; the reviewer opens it.
Where it helps
Anywhere the person who found a problem should be the one to say it is fixed.
Client review
The client who asked for the change confirms it on the page, as a guest if they reviewed through a review link.
Bug reports
The person who reported the bug checks the fix where they found it, rather than the developer closing it unchecked.
Acceptance testing
Testers confirm the fixes for what they reported before a release. Each thread records its own decision; it is not a sign-off of the release.
Try it
Try it on a project of your own, where you choose who checks each fix.
- Sign in and create a project for your site.
- Add the script tag, or open a review link, and leave feedback.
- When a fix is ready, set the thread to Ready to verify and request verification.
Questions
More about uier in the main questions.
Does every thread need verification?
No. It is optional for each thread. There is no project-wide approval step and no custom workflow: Done and Reopen work as before, and a thread waiting for its reviewer can still be marked Done without verification.
Can the person who fixed it confirm it?
No. The requester cannot choose themselves as the reviewer or confirm their own request, not even as an admin. They can still mark the thread done, which is recorded as done without reviewer confirmation.
What if the reviewer is not available?
Request a new check from another member who can see the thread, or ask a workspace admin. An admin decision names the admin and says it was made on the reviewer’s behalf. uier never puts someone else in the reviewer’s place on its own.
Does closing the issue in GitHub or Linear confirm the fix?
No. With two-way status sync, closing the issue in a connected service marks the thread done without reviewer confirmation, and reopening it there reopens the thread. A thread that is ready to verify shows as open there.
Can an AI agent confirm a fix?
No. Through the MCP connector, an agent can request or cancel a check after you approve that exact action. Setting a thread’s status through MCP is an ordinary Done, never a confirmation.
Does it check the fix for me?
No. A person checks the page and decides. uier records the request, the decision, who made it and when. It does not take a second screenshot; the original comment and screenshot stay as they were.
What does it cost?
Nothing. Every feature available today is free and will stay free forever. If we introduce pricing, it will apply only to new features users want.