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

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

Bugs — High/Critical, Open

1. Bugs by Module, Source and Status

Every High/Critical bug currently WITH WHITESHIELD, split by source (Client = client-raised, has a Client Jira link; Internal = raised by us) and status. Tickets already completed by WS and awaiting Client verification (Client Validation) are not counted here - they appear in the Client-only table below.

Module	Client									Internal									With WS	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client
Module	To Do	In Prog	Hold	Sub	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client	To Do	In Prog	Hold	Sub	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client	With WS	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client
Scholarships	7	6	1	14	5	2	8	9	3	0	2	0	2	0	0	1	3	0	16	5	2	9	12	3
Exemptions	9	1	0	10	2	6	5	20	8	0	0	0	0	0	0	0	2	0	10	2	6	5	22	8
Cross-module	0	0	0	0	0	0	0	0	0	5	7	0	12	12	0	13	12	0	12	12	0	13	12	0
Total	16	7	1	24	7	8	13	29	11	5	9	0	14	12	0	14	17	0	38	19	8	27	46	11

24h Created counts genuinely new tickets only. Re-opened Client tickets - each logged as a fresh ticket on the WS board when Client re-opens - are excluded from 24h Created and shown separately under 24h Reopen.

2. Bugs - Created vs Closed (3-Week Trend and Forecast)

Cumulative Created vs cumulative Closed over the last 3 weeks (21 days). Created counts ALL intake - both new and re-opened Client tickets (every Client re-open is logged as a fresh ticket on the WS board); Closed counts tickets closed on the Client board (any Done-category status). The gap between the two lines shows whether the open load is closing (narrowing) or enlarging (widening). Open Trend forecasts the landing point for the items currently with Whiteshield (same scope as the first chart: Client-raised and Internal, High/Critical; items in Client Validation are with Client and outside this balance): a Monte Carlo simulation of 10,000 runs burns down the pending balance at the daily closure throughput observed on the Client board over the last 3 weeks, marking the dates by which all pending items are closed with 50 percent and 85 percent confidence. New intake after today is not modeled.

3. 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	7	6	10	1	24
Exemptions	9	1	14	0	24
Total	16	7	24	1	48

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).

Cross-check vs the by-source table above: the 48 here = 24 with WS + 24 in Client Validation. The With WS total above (38) = 24 Client-raised with WS + 14 Internal - it excludes the 24 in Client Validation, which are with Client for verification.

4. Bugs by Module, Source and Size

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

Module	Client							Internal							With WS
Module	XS	S	M	L	XL	TBD	Sub	XS	S	M	L	XL	TBD	Sub	With WS
Scholarships	0	8	5	1	0	0	14	0	2	0	0	0	0	2	16
Exemptions	5	5	0	0	0	0	10	0	0	0	0	0	0	0	10
Cross-module	0	0	0	0	0	0	0	2	4	2	0	0	4	12	12
Total	5	13	5	1	0	0	24	2	6	2	0	0	4	14	38

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

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

Module	Critical				High				With WS
Module	To Do	In Prog	Hold	Sub	To Do	In Prog	Hold	Sub	With WS
Scholarships	5	1	0	6	2	5	1	8	14
Exemptions	8	0	0	8	1	1	0	2	10
Cross-module	0	0	0	0	0	0	0	0	0
Total	13	1	0	14	3	6	1	10	24

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

6. Improvements by Module, Source and Status

Client-raised improvements currently WITH WHITESHIELD (our type Enhancement = client Improvement) for Scholarships and Exemptions. Items in Client Validation are not counted here - see the Client-only table below.

Module	Client								With WS	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client
Module	To Do	In Prog	Hold	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client	With WS	24h Created	24h Reopen	24h Triaged	24h Closed WS	24h Closed Client
Scholarships	12	1	1	0	0	0	0	0	14	0	0	0	0	0
Exemptions	6	0	1	0	0	0	0	0	7	0	0	0	0	0
Total	18	1	2	0	0	0	0	0	21	0	0	0	0	0

7. Improvements - Created vs Closed (3-Week Trend and Forecast)

8. 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	12	1	2	1	16
Exemptions	6	0	0	1	7
Total	18	1	2	2	23

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).

Cross-check vs the by-source table above: the 23 here = 21 with WS + 2 in Client Validation. The With WS total above (21) = 21 Client-raised with WS - it excludes the 2 in Client Validation, which are with Client for verification.

9. Improvements by Module, Source and Size

The same improvements by T-shirt size.

Module	Client						With WS
Module	XS	S	M	L	XL	TBD	With WS
Scholarships	1	5	4	3	0	1	14
Exemptions	0	4	2	1	0	0	7
Total	1	9	6	4	0	1	21

10. Improvements by Module, Priority and Status

Client improvements by priority and status.

Module	Critical				High				With WS
Module	To Do	In Prog	Hold	Sub	To Do	In Prog	Hold	Sub	With WS
Scholarships	5	0	0	5	7	1	1	9	14
Exemptions	1	0	0	1	5	0	1	6	7
Total	6	0	0	6	12	1	2	15	21

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) = genuinely NEW items raised in the last 24 hours (re-opens excluded); 24h Reopen (purple) = Client re-opens logged in the last 24 hours (each re-open creates a fresh ticket on our board); 24h Triaged (amber) = items moved from Backlog or Triage into Next in the last 24 hours; 24h Closed WS (green) = items resolved to a Done status on the WS board in the last 24 hours, regardless of the Client-side status; 24h Closed Client (teal) = items closed on the Client board 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.