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

Open items (To Do + In Progress + Hold/Blocked) · live snapshot 07 August 2026, 02:45 (GST) · Client Bugs 47 · Internal Bugs 19 · Client Improvements 20 · 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.

ModuleClientInternalTotal24h Created24h Reopen24h Triaged24h Closed WS24h Closed Client
To DoIn ProgHoldSub24h Created24h Reopen24h Triaged24h Closed WS24h Closed ClientTo DoIn ProgHoldSub24h Created24h Reopen24h Triaged24h Closed WS24h Closed Client
Scholarships141012541118513041001029511195
Exemptions610622538148110220200247310148
Cross-module00000000075113201101320110
Total202074794192213991195032066144222413

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 currently pending items (same scope as the first chart: Client-raised and Internal, High/Critical): 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.

10020001940646484126139163192210018334040436676101121134Today 07 AugCreated - cumulative (new + re-opened)Closed on Client board - cumulative18 Jul20 Jul22 Jul24 Jul26 Jul28 Jul30 Jul01 Aug03 Aug05 Aug07 Aug25507566 pending50%: 18 Aug85%: 22 AugToday 07 AugOpen Trend - landing forecast07 Aug09 Aug11 Aug13 Aug15 Aug17 Aug19 Aug21 Aug23 Aug25 Aug

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

ModuleTo DoWS ImplementationClient ValidationHoldTotal
Scholarships141011136
Exemptions61012634
Total202023770

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

1 item(s) currently syncing between the boards (counted once on each side until the next sync): EX-39

4. Bugs by Module, Source and Size

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

ModuleClientInternalTotal
XSSMLXLTBDSubXSSMLXLTBDSub
Scholarships312640025012100429
Exemptions515200022011000224
Cross-module00000002550011313
Total8278400472781011966

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

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

ModuleCriticalHighTotal
To DoIn ProgHoldSubTo DoIn ProgHoldSub
Scholarships331711701825
Exemptions45413252922
Cross-module000000000
Total78520131222747

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

6. Improvements by Module, Source and Status

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

ModuleClientTotal24h Created24h Reopen24h Triaged24h Closed WS24h Closed Client
To DoIn ProgHold24h Created24h Reopen24h Triaged24h Closed WS24h Closed Client
Scholarships1111000001300000
Exemptions60100000700000
Total1712000002000000

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.

7. Improvements - 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 currently pending items (same scope as the first chart: Client-raised and Internal, High/Critical): 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.

1230022222223300000000122Today 07 AugCreated - cumulative (new + re-opened)Closed on Client board - cumulative18 Jul20 Jul22 Jul24 Jul26 Jul28 Jul30 Jul01 Aug03 Aug05 Aug07 Aug102020 pendingToday 07 AugOpen Trend - landing forecastAt the last-3-week closure rate the pending balance is not cleared within 60 days at 50% and 85% confidence.07 Aug09 Aug11 Aug13 Aug15 Aug17 Aug19 Aug21 Aug23 Aug25 Aug27 Aug29 Aug

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.

ModuleTo DoWS ImplementationClient ValidationHoldTotal
Scholarships1112115
Exemptions60017
Total1712222

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

9. Improvements by Module, Source and Size

The same improvements by T-shirt size.

ModuleClientTotal
XSSMLXLTBD
Scholarships15430013
Exemptions0421007
Total19640020

10. Improvements by Module, Priority and Status

Client improvements by priority and status.

ModuleCriticalHighTotal
To DoIn ProgHoldSubTo DoIn ProgHoldSub
Scholarships5005611813
Exemptions100150167
Total600611121420
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.