QA Status Report

Figures as of 13 Aug 2026 · pulled 13 Aug 2026, 23:26

Back to the dashboard

QNB · Project Nile

QA Status Report

Release 1 · Sprint 18

RED

Release confidence

Release 1 meets 2 of 6 exit criteria with 3 sprints remaining.

1 Critical defect remains open across Release 1's current position, including undated blockers.

Figures as of
13 Aug 2026
Data pulled
13 Aug 2026, 23:26 (same day as the last Jira change)
Population
550 defects · 96 open · 454 closed
Exit criteria
2 of 6 met
Source
All four datasets were pulled within 0 hours of each other, oldest Solution Design on 13 Aug 2026.

Contents

  1. 1Executive summaryThe release verdict, and the four figures it rests on.
  2. 2Release readinessEvery exit criterion, its target, and whether it is met.
  3. 3Defect pipelineWhere the unclosed population is sitting today.
  4. 4Work streamsWhich parts of the product carry the open defects.
  5. 5Severity, priority and causeWhat kind of defects these are, and what is causing them.
  6. 6Discovery against closureWhether the team is closing defects faster than it is finding them.
  7. 7Ageing and time in statusHow long open defects have been waiting, against the declared SLA.
  8. 8Defect densityDefects per story delivered, by work stream and by sprint.
  9. 9Rework and concentrationFixes that did not hold, and where they cluster.
  10. 10Epics carrying the defectsThe capabilities the open work is concentrated in.
  11. 11Test execution and coverageWhat has been run, what passed, and what is blocked.
  12. 12Test automationHow much of the linked test population is meant to be automated, and how much is built.
  13. 13What this report cannot tell youThe fields the figures above depend on, and how complete they are.
  14. AAppendix — open defect registerEvery one of the 128 unclosed defects in this export, longest waiting first.

Every figure in this report is measured over the whole export — 550 defects, of which 96 are open — and is frozen to 13 Aug 2026. The dashboard at /qa carries the same figures and can narrow them by sprint and work stream; this document does not, so that what it states is one scope rather than a selection.

Section 1

Executive summary

95% of in-scope requirements have test coverage and 92% of planned tests have been executed. Defect closure exceeded discovery in each of the last two sprints. Release 1 meets 2 of 6 exit criteria with 3 sprints remaining. 1 Critical defect remains open across Release 1's current position, including undated blockers.

Proof points
Requirement Coverage
Why this card can never show a trend
QMetry has no history endpoint — the same constraint behind the frozen badges elsewhere on this page — so this card can never carry a trend, in any sprint. A KPI card with no cue reads as “unchanged”, which would be a claim this export cannot support.

95%

of in-scope requirements covered Source: QMetry

See test evidence

Test Execution
Why this card can never show a trend
QMetry has no history endpoint — the same constraint behind the frozen badges elsewhere on this page — so this card can never carry a trend, in any sprint. A KPI card with no cue reads as “unchanged”, which would be a claim this export cannot support.

92%

of planned tests executed Source: QMetry

See test evidence

Open Critical & Major Defects
What this number is scoped to, and what it ignores
Release 1’s CURRENT position, independent of the sprint or work stream chosen anywhere else on this page. That matters the moment a reader compares it with the Release readiness figures below, which do move with their own control. A missing severity is never defaulted into either count: folding an unset field into Low is how a Critical disappears.

23

+6 vs Sprint 17

Critical + Major, open now Source: Jira

See in Inventory

Blocked testing
Blocked is not failed
A blocked test was attempted and produced NO verdict, so it is not a failure and is not counted as one anywhere on this page. It is also not a pass: the requirement it covers is untested either way, which is why a high blocked share suppresses the execution figure above rather than flattering it.

40%

1,891 of 4,731 test casesSource: QMetry

See blockers

Scope Stability

Not captured — baseline not configured

Section 2

Release readiness

RED2 of 6 criteria met — first not met: No open Critical defects

  • No open Critical defects

    Critical defects still open. None may remain at release.

    Now 1 · target exactly 0 · Not met

  • Requirement coverage

    Requirements with at least one test case written against them.

    Now 95% · target at least 95% · Met

  • Test execution progress

    Test cases attempted at all: passed, failed or blocked.

    Now 92% · target at least 90% · Met

  • Open Major within tolerance

    Major defects still open. A tolerance, not zero.

    Now 23 · target at most 10 · Not met

  • Blocked testing within tolerance (programme scope, includes L3)

    Executions that could not run, usually blocked on an environment.

    Now 34% · target at most 10% · Not met

  • Closure keeping pace with discovery

    Defects closed per defect raised. Below 1.0 the backlog grows.

    Now 0.98 · target at least 1.00 · Not met

Section 3

Defect pipeline

All 550 defects, and how they moved
How to read the lifecycle
A circle is how many defects sit in that status right now; the weight of a line is how many transitions have taken that path since the programme began, which is a total and not a rate. A red ring marks a status whose median dwell is past its SLA — QA measures time IN a status rather than per transition, so the breach belongs on the node. Amber is work coming back: a failed re-test returns to triage, not to the developer, because the fix is disputed before it is redone. Coral leaves the flow at triage. Blue arrives at Closed, whichever way it got there. The changelog also holds 85 transitions through status names this workflow no longer uses — Reopened, Under Analysis, In review and others from before the current ladder. They are counted and not drawn, because a line between statuses the ladder does not name has nowhere to land.
554307532417
ATo Do1d median · 7d SLA
BValidation8d median · 7d SLA
CIn Development0d median · 10d SLA
DPeer review1d median · 5d SLA
EResolved0d median · 5d SLA
FClosedclosed, fixed
54 rejected
29 reopened
20 closed instead
14 sent back to development
188 sent back to triage
GDefect Rejected
Every status, including those at zero
Raised
ATo Do (54)
Triage & re-test
BDefect validation (30)
Fix
CIn Development (7)
DPeer review (5)
Awaiting verification
EDefect Resolved (32)
Closed
FClosed (417)
GDefect Rejected (5)

Section 4

Work streams

Open defects by work stream
Everyday Banking

33Everyday Banking

open R1 defects

All 216 defects

Critical: 0 · Major: 11

Payments & Transfers

31Payments & Transfers

open R1 defects

All 181 defects

Critical: 0 · Major: 10

Cards & Lending

10Cards & Lending

open R1 defects

All 153 defects

Critical: 0 · Major: 2

Value Add

0Value Add

open R1 defects

All 0 defects

Critical: 0 · Major: 0

0 open R1 defects fall outside the four configured work streams.

Section 5

Severity, priority and cause

Severity
A share of what was filled in, not of the population
Severity is 100% populated, so every severity figure on this page is a share of the defects that carry the field. The field's own words are used, and unset is shown rather than defaulted — defaulting an empty severity to Low is how a Critical disappears.
Critical16
Major152
Minor320
Trivial62
unset0

0 defects carry no severity at all.

Priority
Highest163%
High7213%
Medium38670%
Low7614%
unset00%

Priority barely moves closure: every priority with enough closures to measure lands between 11 and 14 days. Medium carries 70% of all defects, so the field is set and then largely ignored.

Root cause

Shares below are of the 43 defects that carry a root cause — 8% of the 550 on this page. The field is filled at triage rather than backfilled, so the mix sharpens as more defects are worked. It also covers the four squad streams only: Integration, which this page excludes, holds more root-caused defects than the four together.

Section 6

Discovery against closure

Defect closure exceeded discovery in each of the last two sprints

Raised against closed

Defects raised vs closed, trailing 6 sprints. Defect closure exceeded discovery in each of the last two sprints.

RaisedClosed

Fixes delivered is not the same figure as closed. It counts a defect’s first arrival at Defect Resolved or Closed, so it reaches 479 where the verdict says 454 closed: 30 defects were fixed and came back, and are open again now.

Open by status, at each sprint end

Open defects by status at each sprint end, trailing 6 sprints. The open pile is up 27 across the window, at 128 today. Sprint 18 has not closed, so its bar is the position at 2026-08-13.

To DoDefect validationIn DevelopmentPeer reviewDefect Resolved
Closed against still open, by sprint raised
Closed by thenStill open

Section 7

Ageing and time in status

Open defects by age
What the clock starts on, and why it ignores the sprint control
Age runs from the day a defect was raised to 13 Aug 2026, the export's own as-of. This block is LIVE TO DATE: a defect does not become younger because a reader narrowed the page to one sprint, so it is the one section here that does not follow a sprint control.
0-6d27
7-13d15
14-29d11
30-59d23
60d+20

43 open defects have been sitting more than 30 days.

How many sprints a defect has been carried
Why the same ageing is shown twice
This is the card above in the unit a delivery forum plans in. A defect carried through several sprints has survived every prioritisation since it was raised, which a day count does not say.
Raised this sprint44
2-3 sprints44
4-6 sprints29
7-9 sprints4
10 or more1
Never in a sprint6
Age by status, against SLA
Open defects per status with the median, mean and oldest age of that queue, and the SLA each is measured against.
StatusOpenMedian ageAverage ageOldestSLA
To Do5415d33d200d7d
Defect validation3044d42d122d7d
In Development77d15d52d10d
Peer review524d23d49d5d

3 of 4 queues sit above their SLA at the median, which means the typical defect there is late rather than a few stragglers being late.

Time spent in each status
Why this disagrees with Ageing, on purpose
Measured over every defect that ENTERED the status, not over what is sitting there now. This is what a step costs; Ageing above is how old the queue is. They disagree by design: a status can clear quickly and still hold defects that never moved.
Median and 90th-percentile time spent in each status, over every defect that entered it, against the SLA declared for that status.
StatusEnteredMedianp90SLA
To Do271d18d7d
Defect validationover SLA4978d57d7d
In Development469<1d9d10d
Peer review4651d14d5d
Defect Resolved461<1d9d5d
Closed417<1d<1d—

1 of 6 statuses run over their declared SLA.

Time spent, not time waiting, and the section above measures the other one. Every visit counts: a defect that bounced back to validation three times spent time there three times, and a figure that counted only the last visit would understate exactly the statuses where rework happens. Defects that never entered a status are left out of its median rather than counted as zero, which would print “fast” where the truth is “most never went there”. The two measures disagree on purpose: To Do clears in about a day yet the 54 defects sitting in it now are far older, because the workflow is quick and a pool of them never moved. Closed and Rejected do not accrue after arrival, so this table is not a second way of reporting backlog age.

Section 8

Defect density

Cumulative and the only fair comparison here: the denominator is the whole stream, so it does not move with how work happened to be scheduled. 43% of stories carry no sprint, so every figure is an upper bound.

Defects per story, by stream
Why this cannot fall when a sprint goes well
The divisor is the stream's WHOLE story count, not the stories in the current sprint, so the ratio does not move with scheduling. 43% of stories carry no sprint at all, so every figure here is an upper bound rather than a measurement.
Everyday BankingEveryday Banking216 / 2490.87
Payments & TransfersPayments & Transfers181 / 842.15
Cards & LendingCards & Lending153 / 2270.67
Value AddValue Add0 / 71untested
Intake against scope in play, by sprint
Two series, not their ratio
Per-sprint density is not a trend on this data. Counting stories by sprint membership makes it fall only because unfinished work accumulates; counting each story once swings it on when planning added tickets. Side by side these show whether intake moved, or scope did.
S12
S13
S14
S15
S16
S17
S18
Defects raisedStories in play

Section 9

Rework and concentration

30% of fixes come back — 188 rejections across 617 submitted fixes. That is the rate, and its denominator is submissions rather than defects: one defect fixed four times is four attempts. Separately, 137 distinct defects (25% of 550) have had at least one fix rejected. Nothing else on this page counts a fix that was made twice.

Fixes that did not hold
What the rate is measured against, and what is not
The bands are declared rather than inferred: green at or under 10%, amber to 20%, red above. They apply to the RATE — bounces over fixes submitted for verification, so one defect fixed four times is four attempts — and to nothing else here. The counts beside it are over all defects and stay descriptive, because a count has no target to breach. Separately, 39 of the 137 bounced more than once: a fix that fails verification twice is not a slow fix, it is a fix aimed at the wrong thing, which is a different problem from the headline rate.

30%

of fixes submitted for verification came back — 188 rejections across 617 submissions. 137 distinct defects (25% of all defects) bounced at least once.

1 time98
2 times28
3 times10
4 times1
Where the rework concentrates
Capability, not squad — and why the join failures stay
Stream says which squad owns a defect; this says which capability is actually breaking. The largest named capabilities hold 40 of the bounced defects. Defects with no parent epic are kept as their own row rather than dropped: they are a join failure, and hiding them would make the concentration look tighter than it is.
no parent epic3023%
Transfers - Local transfers (ACH) (MOCK)1915%
Transfers - Add/Manage Beneficiaries (MOCK)97%
Deposit Accounts (TD/CD) - Break Deposit (MOCK)75%
Credit Cards - Manage card (PIN, freeze, stop) (MOCK)54%
Transfers - Instant transfers (IPN) (MOCK)54%

Section 10

Epics carrying the defects

Two numbers read together, because neither answers alone. A count says an epic is noisy; the same count against a handful of stories rather than a hundred says it is broken. Sorted by defects and then by density for that reason — the epic with the most defects here is 59% delivered, and the one carrying the most per story has barely started. 59 defects — 11% — name no epic this page can find, and are counted here rather than dropped: a rollup that quietly loses rows makes a stream look healthier than it is. Percentage delivered is the epic's own, across all its children, so it counts work this page never sees.

Defects by capability, against progress
What the shares are a share of
The rows above are the largest 12 of 65 capabilities, holding 11% of the defects that could be attributed to one. 59 defects carry no capability at all — blank or absent from the epic export — so they sit in none of these rows and in none of the 491 counted. They are stated rather than dropped, because a join failure that vanishes reads as a capability with no defects.
The capabilities carrying the most defects, with how many are still open, how many stories the capability holds, how far through it is, and defects per story.
EpicCapabilityStreamDefectsOpenStoriesDonePer story
NILE-158Transfers - Add/Manage Beneficiaries (MOCK)Payments & Transfers3759459%0.39
NILE-44Onboarding - Registration (MOCK)Everyday Banking37115392%0.24
NILE-151Transfers - Local transfers (ACH) (MOCK)Payments & Transfers34124085%0.85
NILE-152Transfers - Instant transfers (IPN) (MOCK)Payments & Transfers3447584%0.45
NILE-157Transfers - Manage Recurring Transfers (MOCK)Payments & Transfers2314482%0.52
NILE-132Credit Cards - Manage card (PIN, freeze, stop) (MOCK)Cards & Lending19450%3.80
NILE-2779Transfers - Between My Accounts LCY (MOCK)Payments & Transfers1913485%0.56
NILE-982Onboarding - Splash Screen & Welcome Pages (MOCK)Everyday Banking1916790%0.28
NILE-150Transfers - EZ Bank Internal Transfers (MOCK)Payments & Transfers1841867%1.00
NILE-133Credit Cards - Manage Card Limit (MOCK)Cards & Lending142190%0.74
NILE-124Credit Cards - Application Status Tracker (MOCK)Cards & Lending130100%1.30
NILE-68Deposit Accounts (TD/CD) - Break Deposit (MOCK)Everyday Banking12510100%1.20

Section 11

Test execution and coverage

Evidence

Canonical latest result, 4,731 test cases.

  • Passed 2,288 · 48%
  • Failed 376 · 8%
  • Blocked 1,891 · 40%
  • Not run 176 · 4%

Two denominators, on purpose. Blocked is 34% of all 8,713 executions. Failed is 9% of that same total but 16% of the 5,025 that actually ran. Quoting the first alone would flatter an estate where a third of tests never start, so both appear and this sentence names the gap.

Execution by sprint

Executions per sprint, trailing 6 sprints. Sprint 18 has 744 so far, of which 80% of the ones that ran passed. Its window has not closed — figures are to 2026-08-13. Each bar is work done in that sprint, not a running total.

PassedFailedBlockedNot run
Blocked by environment

Blocked test cases by execution environment, canonical latest result.

  • Dev

    738 blocked, oldest 204d

  • SIT

    1153 blocked, oldest 168d

  • UAT

    No blocked test cases

Blocking is spread across the population rather than concentrated: 2,995 of 8,713 executions across 410 cycles. Dev and SIT are within a point of each other on both blocked and failed, so this is not an environment problem.

Section 12

Test automation

Scope and completion
What these figures do not say
The population is test cases linked to the four squads’ stories, not every test case in NILE. Test execution above is drawn from every cycle in the project, so a percentage here does not read against a count there. Outside scope is a residual rather than a tag: the 2,967 cases there merge cases marked Manual with cases whose Automation Status was never set, and the export cannot separate the two. Effort is reported in steps because that is the only unit the export measures: QMetry records no manual execution time, and the gap between a test entering a cycle and its result being set is calendar latency, not effort. A step is what a tester physically works through, so the counts stand on their own and a reader who knows their own minutes-per-step can do the arithmetic this export cannot. The 542 cases that have never been executed carry no step count anywhere in the export and are outside every step figure, though they remain in the case counts above.

21.5% of the linked test cases are in automation scope, and 44.8% of that scope is built.

Linked test cases
3,780
In automation scope
813
Automated
364
Outside scope (Manual or unset)
2,967
Manual steps now run by machine
1,846
Steps in automation scope
4,160
Steps still to automate
2,314
Cases with no step count
542

1,846 steps run by machine, not by hand — reported in steps, not hours.

Linked test cases only — Test execution above counts a wider population.

Automation funnel
How the stages narrow
Each bar is drawn from the one above it, so the widths read against each other rather than against three separate populations. The drop between the first two is the decision nobody has taken — cases nobody has marked for automation — and the drop between the last two is work planned but not yet built. Of 180 stories carrying test cases, 76 have nothing in automation scope at all and 32 are fully automated.

3,780

100%

Linked test cases

813

21.5%

Planned for automation

2,967 fall out here

364

9.6%

Automated

449 fall out here

Linked test cases: 3780 test cases across 180 stories; Planned for automation: 813 test cases across 104 stories; Automated: 364 test cases across 39 stories
Stories carrying test cases
180
Stories with nothing in scope
76
Stories fully automated
32
Automation build, by sprint
Why this counts tickets, not test cases
QMetry records no history for its Automation Status field and its Open API exposes no audit of a field change, so it cannot say WHEN a case was automated; dating automation by its first automated execution reaches 9 of 363 automated cases. The programme tracks the build work itself in Jira, and a ticket carries a real transition into a done status. Those tickets are this chart. The label covers CI/CD and environment work as well as test-framework components, so the population is wider than the test cases counted above and the two must not be read against each other. Each column is cumulative to the end of that sprint, measured against today's ticket count: Jira cannot say how many tickets existed at an earlier sprint, so scope added since makes early sprints look further from done than they felt.

Jira tickets, cumulative. Not test cases.

43 built · 77 open

35.8%

S11

53 built · 67 open

44.2%

S12

54 built · 66 open

45%

S13

56 built · 64 open

46.7%

S14

61 built · 59 open

50.8%

S15

70 built · 50 open

58.3%

S16

80 built · 40 open

66.7%

S17

87 built · 33 open

72.5%

S18

S11: 43 built, 77 open, of 120 automation tickets; S12: 53 built, 67 open, of 120 automation tickets; S13: 54 built, 66 open, of 120 automation tickets; S14: 56 built, 64 open, of 120 automation tickets; S15: 61 built, 59 open, of 120 automation tickets; S16: 70 built, 50 open, of 120 automation tickets; S17: 80 built, 40 open, of 120 automation tickets; S18: 87 built, 33 open, of 120 automation tickets
Everyday Banking

80.6%Everyday Banking

of automation scope built

344 automated of 427 in scope

from 71 requirements

Cards & Lending

2.2%Cards & Lending

of automation scope built

7 automated of 314 in scope

from 74 requirements

Payments & Transfers

18.1%Payments & Transfers

of automation scope built

13 automated of 72 in scope

from 45 requirements

Value Add

—Value Add

QMetry holds no Value Add requirement — no rate to report, not a rate of zero.

By epic
Why these rows are not the problem set
Rows sort by cases in automation scope, descending, so the epics that fall below the cut are the ones with the least planned. “Nobody intends to automate this” is a finding, and it is precisely the finding a capped list hides. The unlisted epics hold 1,657 linked cases and 116 in automation scope. 364 test cases are linked to more than one story. Such a case counts under each of its stories and once in the total, so these rows can sum to more than the total row — that is the honest arithmetic for a shared test case, not a rounding error. 1 case counts as automated on execution evidence despite a weaker tag. The deflating direction is deliberately not counted, so this is not a score for tag quality.
The epics with the most test cases in automation scope, with how many cases each holds, how many are in scope, how many are automated, and the share of that scope built.
EpicStreamCasesIn scopeAutomatedScope built
no parent epicEveryday Banking1,01129922575.3%
Credit Cards - Apply for Credit Card (Unsecured) (MOCK)Cards & Lending23014600%
Credit Cards - Apply for Credit Card (Secured) (MOCK)Cards & Lending1758900%
Credit Cards - Manage Card Limit (MOCK)Cards & Lending16235720%
Savings Account - View transactions (MOCK)Everyday Banking443333100%
Prepaid Cards - Add / Send Money (MOCK)Cards & Lending633200%
Transfers - Add/Manage Beneficiaries (MOCK)Payments & Transfers31132618.8%
Credit Cards - Make a Card Payment (MOCK)Cards & Lending523000%
Savings Account - View account details (MOCK)Everyday Banking402727100%
Transfers - Instant transfers (IPN) (MOCK)Payments & Transfers3012400%
Savings Account - Open savings account (MOCK)Everyday Banking342222100%
Onboarding - Retrieve Application (MOCK)Everyday Banking221717100%

12 of 48 epics; the rest hold 1,657 linked cases and 116 in scope.

Section 13

What this report cannot tell you

Defect leakage cannot be measured at all.

What this page cannot tell you
Fields the report depends on, how much of each is missing, and which dataset the figure is measured over.
FieldMeasured overMissingShare
Root CauseJira · defects · 55050792%
Area labelJira · defects · 55038069%
Parent epicJira · defects · 5505911%
LabelsJira · defects · 550489%
AssigneeJira · defects · 55031%
EnvironmentJira · defects · 55010%
SeverityJira · defects · 55000%
Environment classifiedJira · defects · 55000%
Build recordedQMetry · executions · 8713736985%
Ran in UATQMetry · executions · 87138713100%
AutomatedQMetry · executions · 8713855798%

Defect Environment is empty on 0% of defects, so leakage — a defect found after it left the build — cannot be measured at all on this export rather than being zero. Each row above is a field somebody owns; the figures on this page are computed over what those fields actually contain, not over what they were meant to.

Appendix A

Open defect register

All 128 unclosed defects, longest waiting first. The 422 closed defects are counted throughout this report and are not listed here.

Every unclosed defect in this export: key, summary, status, priority, work stream, days waiting, the sprint it was raised in and the sprints it has been carried.
KeySummaryStatusPriorityStreamWaitingRaised
NILE-3203Defect- Origination - Validate Email with OTP - User session does not expire after inactivityATo DoHighEDB200dSprint 4
NILE-4336CLONE - Defect - Welcome Flow Screen - App fails to start on Android OS 12EDefect ResolvedMediumEDB177dSprint 6
NILE-7596Defect - Retrieve Application - SMS-OTP screen not triggered on retrieve-applicationBDefect validationMediumEDB122dSprint 9
NILE-8164Defect - Transfers - Internal Transfer - Beneficiary Creation - Nickname Saved as Primary Name Instead of Full NameBDefect validationHighP&T95dSprint 10
NILE-8978Defect - Transfers - ACH - Transfer Details - Notes Field Does Not Sanitize Pasted Content SpacingATo DoMediumP&T94dSprint 12
NILE-9050Defect -Savings Account - View transactions (MOCK) - Savings Account - Filter Transactions - UI defectsATo DoMediumEDB93dSprint 12
NILE-9118Defect - Credit Cards - Freeze/Unfreeze - a cashing issue happens when unfreezing the cardATo DoMediumCL88dSprint 12
NILE-8550Defect - Transfers - Internal Transfer - Transfer Success Screen - Beneficiary Name Font Weight Does Not Match DesignBDefect validationMediumP&T87dSprint 11
NILE-8163Defect - Transfers - Internal Transfer - Beneficiary Creation - QR Scan Incorrect Error Message Displayed for Invalid FormatBDefect validationMediumP&T85dSprint 10
NILE-9133Defect - Credit Card - Apply For a New Card - Card Benefits - (Arabic) there is an extra word, a missing + and ج.م is not added correctly EDefect ResolvedMediumCL85dSprint 12
NILE-9124Defect - Credit Card - Apply For a New Card - Select Collateral accounts (Secured) - (Arabic)some text is not translated and the limits screen sliders are not correct and ج.م is not placed correctlyEDefect ResolvedMediumCL84dSprint 12
NILE-9327Test - Credit Card - Cancel Credit Card (Damaged) - (Arabic) wrong translation in confirmation screen, addresses are not translated and success screen has some wrong translationsBDefect validationLowCL81dSprint 12
NILE-9127Defect -Test execution-Savings Account - Open savings account (MOCK) - Savings Account - Open (Account Benefits) - Translation Defects and unfuntional "create saving account" button on read more pageBDefect validationMediumEDB80dSprint 12
NILE-9154Defect - Transfers - ACH - Transfer Review - Insufficient Balance Validation Not Triggered When Total Amount Exceeds Available BalanceBDefect validationHighP&T80dSprint 12
NILE-9496Defect - Time Deposit Account Filter Transactions - Incorrect Arabic Localization and Translation on Filter ScreenATo DoMediumEDB72dSprint 13
NILE-8535Defect - Share Account Details - Share QR Code option shares text details instead of QR code imageBDefect validationMediumEDB71dSprint 11
NILE-9112Defect - Individual Transactions - Localization issuesBDefect validationLowEDB71dSprint 12
NILE-9529Defect - Time Deposit Account TD - Open Account - Time Deposit Account- Open Time Deposit Account - Review Page - exit deposit creation panel unfunctional "i want to exit" buttonATo DoMediumEDB71dSprint 13
NILE-9540Defect - Time Deposit Account Individual Transactions - Business Requirements in User Story Do Not Match Figma Design for Time Deposit Interest Credit Transaction Details and ReceiptATo DoMediumEDB70dSprint 13
NILE-9604Defect - Time Deposit Account View Recent Transactions - Arabic Localization Needs Review and Refinement on Deposit Details ScreenATo DoMediumEDB67dSprint 14
NILE-9530Defect - Time Deposit Account TD - Open Account - Time Deposit Account- Open Time Deposit Account - Interest & Renewal - translation defectsEDefect ResolvedMediumEDB66dSprint 13
NILE-9621Defect - Copywriting - Transfers - IPN Mobile Number Beneficiary Creation - Error Message Does Not Match Approved Figma CopyATo DoLowP&T66dSprint 14
NILE-9689Defect - Transfers - IPN - Beneficiary Creation - Account Number - Name Field Height Becomes Misaligned When Pasting Text Containing SpacesATo DoMediumP&T65dSprint 14
NILE-9703Defect - Transfers - IPN - Beneficiary Creation IPA - Wrong error message displayed for character limit validationATo DoMediumP&T64dSprint 14
NILE-9803Defect - Break Certificate of Deposit Account - Explore alternative products - Arabic Localization Needs Review on Break Deposit Confirmation Bottom SheetATo DoMediumEDB59dSprint 14
NILE-9812Defect - Break Certificate of Deposit Account - Important Notice bottom drawer - Arabic Localization on "Break Deposit" Screen Contains Non-Professional WordingATo DoMediumEDB58dSprint 14
NILE-9800Defect - Transfers -IPN Transfer - Transfer Details Screen - Multiple Labels Do Not Follow Approved Typography GuidelinesEDefect ResolvedLowP&T57dSprint 14
NILE-9804Defect - Break Time Deposit Account - Breakage Type - Localization issues EDefect ResolvedMediumEDB57dSprint 14
NILE-9892Defect - Break Certificate of Deposit Account - Review Page - Arabic Localization Uses Non-Standard Banking TerminologyATo DoMediumEDB57dSprint 14
NILE-9836Defect - Break Time Deposit Account - Review Page - Localization IssuesEDefect ResolvedMediumEDB54dSprint 14
NILE-9096Defect - Filter Transactions - Transaction Filters Multiple UI/UX, Validation, and State Handling IssuesBDefect validationMediumEDB53dSprint 12
NILE-9925Defect - Break Certificate of Deposit Account - Breakage Type - Arabic Localization on Deposit Breakage Page doesn't Follow Standard Banking TerminologyATo DoLowEDB53dSprint 15
NILE-9936Defect - Break Certificate of Deposit Account - Success Page - Arabic Localization on Deposit Break Success Page Does Not Follow Standard Banking TerminologyATo DoLowEDB53dSprint 15
NILE-8551Defect - Transfers - Internal Transfer - Transfer Success Screen - Incorrect Currency Display in Arabic InterfaceBDefect validationMediumP&T52dSprint 11
NILE-9044Defect - Enhanced Due Diligence - Incorrect Copy Casing Across EDD ScreensCIn DevelopmentMediumEDB52dSprint 12
NILE-9938Defect - Certificate of Deposit Account Edit Deposit Details - Arabic Localization Missing on Auto-Renewal Options Bottom SheetBDefect validationMediumEDB52dSprint 15
NILE-10058Defect - Profile & Settings- View Policies - Display T&Cs Details - Arabic Terminology in Terms & Conditions Screen Requires UX/Localization ReviewATo DoLowEDB50dSprint 15
NILE-10061Defect - Profile & Settings- View Policies - View Fees & Charges - Arabic Localization on Fees & Charges Screen does not Follow Banking Terminology StandardsATo DoLowEDB50dSprint 15
NILE-7542Defect - Onboarding - Username Creation - Input Cursor Appears Too Large in Username and Password Fields When App Language Is ArabicDPeer reviewMediumEDB49dSprint 9
NILE-6956Defect - Debit Card - Freeze/Unfreese - Card Box Model dimensions incorrectly constrained compared to Figma designBDefect validationMediumCL44dSprint 8
NILE-9282Defect - Credit Card - Cancel Credit Card (lost/stolen) - (arabic) confirmation screen is not translated correctlyBDefect validationLowCL44dSprint 12
NILE-9440Defect - Credit Card - Apply For a New Card- Enter Personal Information (Unsecured) - UI and validation issuesBDefect validationLowCL44dSprint 13
NILE-10327Defect - Default Login Page - Requirements gapsATo DoMediumEDB40dSprint 15
NILE-10328Defect - Biometric Login enabled - Requirements gapsATo DoMediumEDB40dSprint 15
NILE-10329Defect - Forgot Credentials (Scan ID + Liveness Detection) - Requirements gapsATo DoMediumEDB40dSprint 15
NILE-10330Defect - Forgot Username (Select channel & Issue existing username) - Requirements GapsATo DoMediumEDB40dSprint 15
NILE-10232Defect - Beneficiary Management - View Beneficiary Details - Within EZBank - Nickname Field Allows More Than 50 Characters During EditBDefect validationMediumP&T39dSprint 15
NILE-10126Defect - Credit Card - Apply For a New Card - Facilities Declaration (IScore Check) - bank filter drawer issuesDPeer reviewMediumCL38dSprint 15
NILE-10378Defect - Individual Transactions - Requirements gapsATo DoMediumEDB38dSprint 16
NILE-6044Defect - Payments & Transfers Dashboard - UI "Add new beneficiary" Text Wrapping and Container Heigh Incorrect in English and arabic (Not Matching Figma)BDefect validationMediumP&T32dSprint 7
NILE-8075Defect - Onboarding - Username & Password Creation - Continue Button UI/Design Issue When Keyboard Is DisplayedCIn DevelopmentMediumEDB29dSprint 10
NILE-10625Defect - General - Input Field Becomes Unresponsive After Dismissing the KeyboardATo DoMediumEDB28dSprint 16
NILE-9098Defect - Filter Transactions - Load More Button Appears When No More Transactions Exist After FilteringBDefect validationLowEDB25dSprint 12
NILE-9536Defect - Transfers - IPN - Beneficiary Selection - Beneficiary Search Returns Results Based on Instapay Address Instead of Beneficiary Name or NicknameBDefect validationMediumP&T25dSprint 13
NILE-10368Defect - Individual Transactions - Balance and amount are not displayed with decimals and dispute transaction CTA is missing BDefect validationMediumEDB24dSprint 16
NILE-10561Defect - General - Regression testing - CASA - Saving Account - Screen Is Not ScrollableDPeer reviewMediumEDB24dSprint 16
NILE-10136Defect - Profile & Settings - Logout - App Log out - Logout Confirmation Bottom Sheet UI issuesBDefect validationMediumEDB22dSprint 15
NILE-10624Defect - Onboarding - eKYC (DFI BYPASS) - Origination - eKYC Success Screen Does Not Match Figma Design (Icon and Spacing)ATo DoMediumEDB18dSprint 16
NILE-10897Defect - Regression - Prepaid Card - generate statement - the user is able to choose future datesATo DoLowCL17dSprint 17
NILE-11185Defect - Debit Card - Card Issuance - Discrepancies in NI API Triggering, Messaging, & SLA BehaviorsATo DoMediumCL15dSprint 17
NILE-11207Defect - Splash Screen Continuously Reloads on First App Launch in ArabicATo DoHighestEDB14dSprint 17
NILE-9541Defect - Prepaid Card - Cancel Card (Damaged) - Multiple UI mismatches on Cancel Card flow and Add Address screen compared to FigmaEDefect ResolvedMediumCL11dSprint 13
NILE-11286Defect - API - Device Compatibility API - Session ID is not returned in the response headers and is not documented in the API specificationATo DoHighEDB11dSprint 18
NILE-11287Defect - Business / UI - ACH -ACH Transfer Displays "Transfer Successful" Instead of "Transfer Submitted Successfully"ATo DoMediumP&T11dSprint 18
NILE-11288Defect - Business / UI - Manage Recurring Transfer - Future-Dated Recurring Transfer Displays "Recurring Payment Added Successfully" Instead of "Recurring Payment Submitted Successfully"ATo DoMediumP&T11dSprint 18
NILE-11291Defect - API - [GET] api/v1/professions/{countryId} - Professions API returns an irrelevant salaryRanges field when used for PEP-only flagATo DoMediumEDB11dSprint 18
NILE-11301Defect - Financial Information (Tax Declaration) - Other Nationality flow does not match Figma: nationality field appears automatically and the section is not reset after deleting the first nationalityATo DoLowEDB11dSprint 18
NILE-10390Defect - Beneficiary Management - View Beneficiary Details ACH - Success Snackbar Overlaps "Transfer Money" Button After Editing BeneficiaryBDefect validationLowP&T10dSprint 16
NILE-10393Defect - Beneficiary Management - View Beneficiary Details - UI Inconsistencies on Beneficiary Details ScreenBDefect validationLowP&T10dSprint 16
NILE-10858Defect - eKYC Screens - Close (X) icon is incorrectly displayed on the eKYC screensCIn DevelopmentMediumEDB10dSprint 17
NILE-10860Defect - Transfers - Reactivate Recurring Transfer - Purpose Options Are Not Loaded When Reactivating a Paused Recurring TransferBDefect validationHighP&T10dSprint 17
NILE-11450Cybersecurity Recommendations L1 - Credit Card Application Decisioning - Adherence Tracking ATo DoHighestCL9dSprint 18
NILE-11451Defect - Credit Card - Apply for Unsecured Credit Card - "Something Went Wrong" Generic Error Shown on Tapping ContinueEDefect ResolvedMediumCL9dSprint 18
NILE-11455Cybersecurity Recommendations L2 - Prepaid Card Top Up/Send Money - Adherence Tracking ATo DoMediumCL9dSprint 18
NILE-10811Defect - Transfers - Between My Accounts - Transfer Details - Transfer Review Screen Displays Old Note When Only Note Field Is UpdatedBDefect validationMediumP&T8dSprint 17
NILE-11499Defect - Beneficiary Management - Beneficiary selection - Mobile Number Beneficiary Incorrectly Displays Transfer Type Selection DrawerATo DoHighP&T8dSprint 18
NILE-10208Defect - Credit Card - Apply for Credit Card Unsecured - Multiple UI display issues on benefits, interest rate, credit limit, and submit buttonEDefect ResolvedMediumCL7dSprint 15
NILE-10302Defect - Prepaid Card - Send Money & Top-Up - Multiple UI and functional defectsEDefect ResolvedMediumCL7dSprint 15
NILE-10558Defect - Setup Recurring Payments - Add Recurring Payment - Recurring Transfer Details Persist When Changing BeneficiaryCIn DevelopmentMediumP&T7dSprint 16
NILE-11448Defect -Beneficiary Management - Beneficiary Creation - Application Remains on OTP Screen After Successful OTP VerificationEDefect ResolvedHighestP&T7dSprint 18
NILE-11486Defect - Transfers - ACH - Newly Created Beneficiary Is Not Recognized After Enabling "Save Beneficiary"EDefect ResolvedHighestP&T7dSprint 18
NILE-11511Defect -Beneficiary Management - beneficiary management flows (beneficiaries list screen- add new beneficiary - transfer details - review page - success screen ) dosen't display network error message when there is a network errorATo DoMediumP&T7dSprint 18
NILE-10557Defect - Setup Recurring Payments - Add Recurring Payment - System Allows Invalid Start and End Date Combination and Causes Application to Crash EDefect ResolvedHighP&T4dSprint 16
NILE-11524Defect - Transfers - ACH - Beneficiary List Displays Mobile Number BeneficiariesATo DoHighP&T4dSprint 18
NILE-11525Defect - Transfers - ACH - OTP Verification Is Incorrectly Required During Beneficiary CreationATo DoHighP&T4dSprint 18
NILE-11538Defect - Transfers - ACH - Beneficiary List Displays More Beneficiaries Than Returned by the BackendATo DoHighP&T4dSprint 18
NILE-11539Defect - Backend API - POST /cards/{cardId}/sdk-token Response Schema Missing Mandatory Confluence Fields (cardIdentifierId, bankCode)ATo DoHighestCL4dSprint 18
NILE-11540Defect - Backend API - GET /cards/{cardId}/status Multiple Issues: Masked PAN Format Mismatch, Missing Correlation-Id Header Allowed, & 500 Returned on Missing CardATo DoHighCL4dSprint 18
NILE-11541Defect - Transfers - ACH - Beneficiary Search Returns Non-Matching ResultsATo DoMediumP&T4dSprint 18
NILE-11542Defect - Transfers - ACH - Add Beneficiary - Duplicate Nickname Is AllowedATo DoMediumP&T4dSprint 18
NILE-11543Defect - UI/UX - Transfers - ACH - Add Beneficiary - Missing Error State for Duplicate NicknameATo DoMediumP&T4dSprint 18
NILE-11545Defect - Backend API - POST /cards/limits Returns 200 OK for Outdated Bank-App-Version (0.1.0) Instead of 400 Bad RequestATo DoMediumCL4dSprint 18
NILE-11547Cybersecurity Recommendations L1 - Credit & Prepaid - Cancel/Replace Card - Adherence Tracking ATo DoHighCL4dSprint 18
NILE-9108Defect - Credit card - cards details screen - UI issues with the card details in the arabic version of the appEDefect ResolvedMediumCL3dSprint 12
NILE-10121Defect - Transfers - Beneficiary Creation - Newly Created Beneficiary Does Not Appear in Recent Beneficiaries SectionEDefect ResolvedHighP&T3dSprint 15
NILE-10490Defect - Beneficiary Management - Beneficiary Creation Success Screen - Incorrect Beneficiary Type Displayed for IPN BeneficiariesEDefect ResolvedMediumP&T3dSprint 16
NILE-10537Defect - Transfers - Setup Recurring Transfers (MOCK) - Setup Recurring Payments - Add Recurring Payment (Success Page) - between my accounts sucess page doesn't display correct destination account typeEDefect ResolvedMediumP&T3dSprint 16
NILE-10565Defect - Cards (Credit / Debit / Prepaid) - Cancel Card (Compromised) - Multiple UI and localization defectsEDefect ResolvedHighCL3dSprint 16
NILE-10885Defect - Setup Recurring Payments - Add Recurring Payment - Beneficiary List Displays "No Beneficiaries Found" Despite Successful API ResponseEDefect ResolvedHighP&T3dSprint 17
NILE-11205Defect - EZ Bank Internal Transfers - Beneficiary Search Returns Results Using Unsupported Account Number and IBANEDefect ResolvedMediumP&T3dSprint 17
NILE-11284Defect - Transfer - ACH - Transfer Amount Field Accepts Values Below the Minimum Allowed AmountEDefect ResolvedMediumP&T3dSprint 18
NILE-11285Defect - Transfers - In All Transfer Flows - Account Name Is Inconsistent Between Transfer Details and Transfer Review ScreensEDefect ResolvedMediumP&T3dSprint 18
NILE-11552Defect - Integration Testing - Login - Default Login Page (Normal Sign In) - User Is Redirected to Dashboard Instead of Digital Debit Card Activation Screen After Account OpeningATo DoHighEDB3dSprint 18
NILE-11556Defect - Beneficiary Creation - Full Name Field Accepts Invalid CharactersEDefect ResolvedHighP&T3dSprint 18
NILE-11560Defect - L1 GET /policies/documents/{id} - Get Policy Document API Accepts Request Without Required id Path ParameterATo DoMediumEDB3dSprint 18
NILE-10134Defect - Profile & Settings- View Policies - Display T&Cs Details - Business Requirement Mismatch – Search Functionality Exists in Figma but Is Not Defined in the User StoryEDefect ResolvedMediumEDB2dSprint 15
NILE-10187Defect - Decision Engine - Custom Database Exporter - EZBank_Camunda_Exporter_Testing_Guide - Process Instance Table Is Not Updated with Service Task When _Exclude Is Removed from Service TaskCIn DevelopmentMediumEDB2dSprint 15
NILE-10189Defect - Decision Engine - Custom Database Exporter - EZBank_Camunda_Exporter_Testing_Guide - start_event_timestamp is not populated when a Process Instance StartsCIn DevelopmentMediumEDB2dSprint 15
NILE-10548Defect - Prepaid Card - Request Prepaid Digital Card - Activation Success Screen - Button unresponsive and back navigation loopEDefect ResolvedHighCL2dSprint 16
NILE-10566Defect - Prepaid Card - View Single Transaction Details - Missing data in transaction details screenEDefect ResolvedHighCL2dSprint 16
NILE-10890Defect - Credit card - Close / Replace Card - Multiple UI and localization mismatches compared to Figma designCIn DevelopmentMediumCL2dSprint 17
NILE-11313Defect - Validation error responses return only a single error message instead of all violated constraints (Transfers Quote API)DPeer reviewMediumP&T2dSprint 18
NILE-11443Defect -API-POST {{baseUrl}}/{{paymentsTrasnfersService}}/transfers/{{transferType}}/{{$guid}}/cancel - Returns success 202 with any GUID format(non-existing transaction)EDefect ResolvedMediumP&T2dSprint 18
NILE-11502Defect -Transfers - ACH Transfer - Transfer Details - failed to navigate to review page when set as recurring payment option is enabled or disabled and amount is 1 EGPEDefect ResolvedLowP&T2dSprint 18
NILE-11544Defect - API - post/beneficiary - Create Beneficiary - Duplicate Nickname Is AllowedEDefect ResolvedMediumP&T2dSprint 18
NILE-11576Cybersecurity L1 Recommendation Credit Card Payment & Auto Payments - Adherence TrackingATo DoHighCL2dSprint 18
NILE-11584Defect - API - GET /accounts/savings/interest-rates - Currency and interest calculation inputs are missing from APIATo DoHighEDB2dSprint 18
NILE-11546Defect - Transfers - ACH -Add Beneficiary - "Save Beneficiary" Toggle Is Removed and Beneficiary Is Always SavedEDefect ResolvedHighP&T1dSprint 18
NILE-11610Defect\Enhancement - General - Add Clear (X) Icon to Search BarsATo DoMediumP&T1dSprint 18
NILE-9856Defect - Credit Card -Apply For a New Card - Request Credit Limit (Secured) - upgarde card behavior is not correctBDefect validationMediumCL<1dSprint 14
NILE-9907Defect - Credit Card - Apply For a New Card - Connected Parties Declaration (Secured)BDefect validationMediumCL<1dSprint 14
NILE-10160Defect - all cards - cancel card (lost/stolen) - unable to navigate from manage limit screen unless doing a changeBDefect validationHighCL<1dSprint 15
NILE-10786Defect - Credit Card - Adjust Limit - Increase limit (Unsecured) - no pop up appearsBDefect validationMediumCL<1dSprint 17
NILE-10884Defect - Credit Card - Increase Limit - wrong redirection to edit financial detailsBDefect validationLowCL<1dSprint 17
NILE-11551Defect - Beneficiary Management - Beneficiary Module Does Not Display a Loading StateEDefect ResolvedMediumP&T<1dSprint 18
NILE-11569Defect - Pre login checks - Incompatible device flow skips “Your device isn’t compatible” screenDPeer reviewLowEDB<1dSprint 18
NILE-11618Defect- Transfers - Ach "General"- Beneficiary Creation Through Transfer Flow Does Not Define When the Beneficiary Is SavedATo DoMediumP&T<1dSprint 18
NILE-11619Defect - Business Requirement -Transfers - ACH - Duplicate Beneficiary Nickname Rule Is Not DefinedATo DoMediumP&T<1dSprint 18