Aman-Mittal opened a new issue, #797:
URL: https://github.com/apache/fineract-backoffice-ui/issues/797

   #### Summary
   The loan, savings and fixed-deposit pages show "Client: {name}" as plain 
text, so the account can't lead back to its owner. The breadcrumbs above these 
pages are also inconsistent:
   - the **loan** page has none;
   - the **savings** and **fixed-deposit** pages read **Products › Savings 
Account Details** / **Products › Fixed Deposit Account Details**, which files a 
customer's account under product configuration.
   
   #### Current behavior
   
   | Page | Client reference | Breadcrumb |
   |---|---|---|
   | `/loans/view/:id` | "Client: E2EAudit DepositClient" (plain `<span>`) | 
none |
   | `/products/savings-accounts/view/:id` | "Client: …" (plain text) | 
Products › Savings Account Details |
   | `/products/fixed-deposits/view/:id` | "Client: …" (plain text) | Products 
› Fixed Deposit Account Details |
   | `/clients/view/:id` | — | Clients › Client Details |
   
   The **Back** button relies on browser history. After a deep link, a page 
reload, or arriving from the dashboard or a search result, it doesn't return to 
the client.
   
   #### Expected behavior
   - The client name on every account page links to the client.
   - Account pages share one breadcrumb pattern that reflects how operators 
think about the record: **Clients › {client} › {account type} {account no}**. 
Group-owned accounts use **Groups › {group} › …**.
   - Breadcrumb segments are links, and the current page is marked 
`aria-current="page"`.
   
   #### Steps to reproduce
   1. Open a client and go to the **Loan Accounts** tab. Open a loan.
   2. Try to return to the client from the loan page: the client name isn't 
clickable and there's no breadcrumb.
   3. Open a savings account from the client page. The breadcrumb reads 
"Products › Savings Account Details", and clicking "Products" leads to product 
configuration, not the client.
   
   #### User impact
   - Servicing work moves constantly between a client and their accounts: post 
a repayment, check savings, return to the client. Each round trip needs the 
sidebar and a fresh search.
   - The "Products" breadcrumb sends users to configuration screens they may 
not be permitted to see, and blurs the line between products (configuration) 
and accounts (customer records).
   - Screen-reader and keyboard users get no orientation landmark on the loan 
page.
   
   #### Evidence
   The savings account header: the client is shown as plain text and the 
breadcrumb says "Products".
   
   ![Account header with unlinked client name and Products 
breadcrumb](https://raw.githubusercontent.com/Aman-Mittal/fineract-backoffice-ui/assets/issue-screenshots/ux-audit-2026-10-16/account-header-client-not-linked.svg)
   
   DOM check on the loan page: the "Client: …" element is a `SPAN` with no link 
ancestor, and the page has no breadcrumb element at all.
   
   #### Proposed improvement
   - Render the owner (client or group) as a `routerLink` in each account 
header.
   - Give the loan, savings, fixed-deposit, recurring-deposit and share account 
pages the shared breadcrumb component, with an owner-based trail.
   - Keep **Back**, but make its fallback target the owner page when there's no 
in-app history.
   
   #### Acceptance criteria
   - [ ] On every account detail page, the owner name links to the owner's page.
   - [ ] Account pages show an owner-based breadcrumb with working links. None 
of them shows "Products" for a customer account.
   - [ ] The breadcrumb has `nav` semantics and `aria-current` on the last item.
   - [ ] Opening an account by deep link and pressing Back lands on the owner 
page.
   
   #### Verification status
   Reproduced on the deployed `main` (2026-10-16), superuser, tenant `default`, 
on loan #1, savings #6 and fixed deposit #1.
   
   #### Related API capabilities
   None needed. The `clientId` / `groupId` and names are already in the account 
responses the pages load.
   
   Related: #767 (a group loan shows a blank client and no group link).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to