UAT results & issue states
How a UAT scenario's result is recorded and read on the UAT tab: the per-tester pass checkbox, the Pass/Fail rollup, and the states a linked issue moves through.
The pass checkbox
Each scenario row has one pass checkbox per tester taking part in UAT. Your own column is shown first and is the only one you can tick — everyone else's column is visible but read-only to you.
Ticking your pass checkbox means: "I ran this scenario and it behaved exactly as the Expected result described." Leaving it un-ticked simply means you haven't passed it — whether you haven't run it yet, or it didn't behave correctly. There's no separate untested, blocked, fail, or N/A value: a scenario is either passed by you or not, and anything that doesn't behave as expected becomes an issue.
Because each tester has their own column, you can see at a glance who has confirmed each scenario. One tester's tick is independent of another's.
The Pass/Fail rollup
Each row also has a read-only Pass/Fail column that summarises whether the scenario has passed overall. It is ticked (pass) only when both of these are true:
- At least one tester has ticked their pass checkbox on the row, and
- There is no open issue linked to the scenario.
For this rule, a linked issue counts as open if it has not yet been accepted by the customer and is not marked Won't do. So:
- A scenario nobody has passed yet → rollup is not ticked.
- A scenario a tester has passed, with no linked issue → rollup is ticked.
- A scenario a tester has passed, but with a linked issue that hasn't been accepted (and isn't Won't do) → rollup stays un-ticked until that issue is resolved and accepted.
In short, a linked issue keeps the rollup un-ticked until it's both resolved and accepted by you.
Raising an issue from a scenario
When a scenario doesn't behave as expected, click the 🚩 flag in the raise-issue column on that row. This opens the New Issue form, pre-filled with a title like UAT fail: <test code> — <scenario title> and automatically linked to the scenario. Complete or cancel the form as you would any issue — see Run UAT for the full flow.
A single scenario can carry more than one linked issue. They appear together on the row (for example, as flag icons with issue numbers like ⚑ #3 #4), and every open one keeps the rollup un-ticked.
Issue states on the UAT grid
A linked issue shows on the scenario's row and moves through these states. Only the last two stop it blocking the Pass/Fail rollup:
| State on the UAT grid | What it means | Blocks rollup? |
|---|---|---|
| Open / In progress / Blocked | The issue has been raised and FullClarity hasn't resolved it yet. | Yes |
| FullClarity-fixed, awaiting acceptance | FullClarity has marked the issue Done. It stays visible as a green link until you confirm the fix. | Yes |
| Accepted | You clicked Accept on the issue — the fix is confirmed good. The issue stays Done but no longer blocks the scenario. | No |
| Won't do | Everyone agreed not to action the issue. It no longer blocks the scenario. | No |
Accepting or reopening a fix
When FullClarity marks a linked issue Done, it does not clear automatically — it stays as a green link on the scenario and keeps the rollup un-ticked until you decide:
- Accept — you confirm the fix is good. The issue stops blocking the rollup (the scenario can now roll up to a pass, provided a tester has ticked their pass column). The issue's status stays Done.
- Reopen — the fix didn't work. The issue goes back to Open and again blocks the rollup.
Acceptance controls live on the issue's notes panel, reached by clicking the issue link from the UAT tab, or from the Notes cell on the Issues tab.
What a healthy UAT picture looks like
As an engagement progresses, you want every in-scope scenario to end up with its Pass/Fail rollup ticked — meaning a tester has passed it and any issues it threw up have been resolved and accepted. Scenarios with un-ticked rollups are the ones still needing attention: either nobody has run them, or they still have an open or unaccepted issue. The grid is, in effect, your live UAT checklist right up to go-live.
Related
- Run UAT — the testing workflow end-to-end.
- Log an issue — including the issue raised from a scenario's flag.
- Issue fields — what the linked-to issue captures.