Cross-Module UAT — Open High/Critical Bugs & Improvements

Open items (To Do + In Progress + Hold/Blocked) · live snapshot 04 August 2026, 14:30 (GST) · Client Bugs 51 · Internal Bugs 14 · Client Improvements 19 · Internal Improvements 0 · tap any number to open that slice in Jira.

Bugs — High/Critical, Open

1. Bugs by Module, Source and Status

Every open High/Critical bug, split by source (Client = client-raised, has a Client Jira link; Internal = raised by us) and status.

Module	Client								Internal								Total	24h Created	24h Re-open	24h Triaged	24h Closed
Module	To Do	In Prog	Hold/Blocked	Sub	24h Created	24h Re-open	24h Triaged	24h Closed	To Do	In Prog	Hold/Blocked	Sub	24h Created	24h Re-open	24h Triaged	24h Closed	Total	24h Created	24h Re-open	24h Triaged	24h Closed
Scholarships	6	10	10	26	1	1	4	8	0	4	0	4	0	0	0	0	30	1	1	4	8
Exemptions	4	16	5	25	5	2	3	3	0	0	0	0	0	0	0	0	25	5	2	3	3
Cross-module	0	0	0	0	0	0	0	0	5	4	1	10	0	0	0	2	10	0	0	0	2
Total	10	26	15	51	6	3	7	11	5	8	1	14	0	0	0	2	65	6	3	7	13

24h Created counts both new and re-opened Client tickets - every Client re-open is logged as a fresh ticket on the WS board. The 24h Re-open column shows how many of the 24h Created items are re-opens; 24h Created minus 24h Re-open = genuinely new intake.

2. Bugs (Client only) by Module and Status

Where the Client-raised bug load stands. To Do and WS Implementation reflect our board (linked to our Jira - To Do = not started, WS Implementation = in progress); Client Validation and Hold are pulled live from the Client Jira board and linked there (Validation = Deployed to staging + In Staging testing, completed by WS and awaiting Client verification).

Module	To Do	WS Implementation	Client Validation	Hold	Total
Scholarships	6	10	20	9	45
Exemptions	4	16	2	5	27
Total	10	26	22	14	72

Total = To Do + WS Implementation (open with WS, from WS Jira) + Client Validation (completed by WS, awaiting Client verification, from Client Jira) + Hold (from Client Jira).

3. Bugs by Module, Source and Size

Same bugs by T-shirt estimation size, split Client vs Internal.

Module	Client							Internal							Total
Module	XS	S	M	L	XL	TBD	Sub	XS	S	M	L	XL	TBD	Sub	Total
Scholarships	4	12	8	2	0	0	26	0	2	1	1	0	0	4	30
Exemptions	5	18	1	0	0	1	25	0	0	0	0	0	0	0	25
Cross-module	0	0	0	0	0	0	0	1	4	5	0	0	0	10	10
Total	9	30	9	2	0	1	51	1	6	6	1	0	0	14	65

4. Bugs (Client only) by Module, Priority and Status

Client-raised bugs by priority (Critical = Client Highest, High = Client High) and status.

Module	Critical				High				Total
Module	To Do	In Prog	Hold/Blocked	Sub	To Do	In Prog	Hold/Blocked	Sub	Total
Scholarships	2	4	4	10	4	6	6	16	26
Exemptions	3	4	2	9	1	12	3	16	25
Cross-module	0	0	0	0	0	0	0	0	0
Total	5	8	6	19	5	18	9	32	51

Client Improvements — High/Critical, Open (Scholarships & Exemptions)

5. Improvements by Module, Source and Status

Client-raised improvements (our type Enhancement = client Improvement) for Scholarships and Exemptions.

Module	Client							Total	24h Created	24h Re-open	24h Triaged	24h Closed
Module	To Do	In Prog	Hold/Blocked	24h Created	24h Re-open	24h Triaged	24h Closed	Total	24h Created	24h Re-open	24h Triaged	24h Closed
Scholarships	11	1	1	0	0	0	0	13	0	0	0	0
Exemptions	2	0	4	0	0	0	0	6	0	0	0	0
Total	13	1	5	0	0	0	0	19	0	0	0	0

6. Improvements (Client only) by Module and Status

Where the Client-raised improvement load stands. To Do and WS Implementation reflect our board (linked to our Jira); Client Validation and Hold are pulled live from the Client Jira board and linked there.

Module	To Do	WS Implementation	Client Validation	Hold	Total
Scholarships	11	1	2	1	15
Exemptions	2	0	0	3	5
Total	13	1	2	4	20

Total = To Do + WS Implementation (open with WS, from WS Jira) + Client Validation (completed by WS, awaiting Client verification, from Client Jira) + Hold (from Client Jira).

7. Improvements by Module, Source and Size

The same improvements by T-shirt size.

Module	Client						Total
Module	XS	S	M	L	XL	TBD	Total
Scholarships	1	5	4	3	0	0	13
Exemptions	0	3	2	1	0	0	6
Total	1	8	6	4	0	0	19

8. Improvements by Module, Priority and Status

Client improvements by priority and status.

Module	Critical				High				Total
Module	To Do	In Prog	Hold/Blocked	Sub	To Do	In Prog	Hold/Blocked	Sub	Total
Scholarships	5	0	0	5	6	1	1	8	13
Exemptions	0	0	1	1	2	0	3	5	6
Total	5	0	1	6	8	1	4	13	19

Hold/Blocked logic. Isolates items paused outside active development: a Client item whose Client Jira Status contains "Hold", or an Internal item that is Flagged (blocked). Shown as their own status and removed from To Do / In Progress.

Scope. High/Critical only, open (To Do, In Progress or Hold/Blocked). Bugs cover Scholarships, Exemptions and Cross-module; Client Improvements cover Scholarships and Exemptions only. Numbers are a live snapshot.

Source. Client = carries a Client Jira link (raised/tracked on the client board). Internal = raised by our team, no client link. Improvements shown are Client-raised only.

24h columns. Throughput context, not part of the open counts, split by source: 24h Created (red) = items raised in the last 24 hours - this includes both NEW and RE-OPENED tickets from the Client side, because every re-open is logged as a fresh ticket on our board; 24h Re-open (purple) = the re-opened subset of 24h Created, so Created minus Re-open = genuinely new intake; 24h Triaged (amber) = items moved from Backlog or Triage into Next in the last 24 hours; 24h Closed (green) = items whose status moved to a Done category in the last 24 hours.

Excluded — Admissions. All Admissions bugs (v1 and v2, Client and internal) are excluded from this view and tracked separately in the planned Admissions releases and the full Cross-Module UAT report.