Aman-Mittal opened a new issue, #419: URL: https://github.com/apache/fineract-backoffice-ui/issues/419
## Business value A branch runs on a small number of routine tasks: open an account, approve what is waiting, reconcile the ledger, re-run a failed batch, answer an auditor. Each of these has a screen in this application, and each screen stops just short of the thing the role actually needs — so the work continues in a spreadsheet, in the API, or in whatever system the institution used before this one. None of these gaps is individually dramatic, which is why none of them has been filed on its own. Together they are why a branch does not run its day out of the back office. ## The gaps | # | Gap | Effect on the branch | |---|---|---| | 1 | No breadcrumb trail, no keyboard navigation | Screens sit several levels deep with nothing saying where the user is or how to get back up. Every section change is a trip through the sidebar. | | 2 | Create-client is one long undifferentiated form | Legal form, office, staff, names, dates, address and contacts are shown at once, with no indication which handful are required. Account opening is done by the least experienced staff under the most time pressure, and this is where they stall. | | 3 | No loan portfolio view | "How much is outstanding, where, and how much is at risk" cannot be answered without exporting to a spreadsheet, though the advanced search endpoint already answers it. | | 4 | Journal entries filter by date only | On a multi-branch tenant, date is the one dimension that narrows nothing. Reconciling one branch's cash account means paging through everything the institution posted that day. | | 5 | Bulk import omits every transactional entity | Loan repayments, savings, fixed- and recurring-deposit transactions — the files a branch or agent network loads daily — cannot be imported. | | 6 | **Bug:** the chart-of-accounts import template is the wrong file | `glaccounts` calls the journal-entries template endpoint. Anyone importing a chart of accounts downloads a template that cannot be imported. | | 7 | Scheduler jobs run one at a time | Recovering from a failed nightly batch means re-running a specific set of jobs individually — slow, and easy to get wrong under pressure. | | 8 | Work queues are one flat institution-wide list, and reschedules can only be approved | A branch approver picks their own rows out of every other branch's. A reschedule request can be approved but never declined, though declining is at least as common. | | 9 | The audit log cannot leave the screen | An auditor or regulator asking what changed and who approved it gets screenshots. | ## Scope In scope: the nine gaps above, each on the screen that already exists for it. Out of scope, tracked separately: - **#197** — savings servicing parity. Undo-approval is the one item taken from that list here, because it is the one that loses data when missing: rejecting and re-keying loses the application date and the account number. The rest stays on #197. - **#295** — term-deposit servicing. The charges and interest-rate-chart tabs are taken here, because an account opened before a product rate change could not be checked against the terms it was actually sold on. The lifecycle actions stay on #295. - **#376** — GLIM and GSIM, which the platform refuses on PostgreSQL. No screens, because a screen for either could only ever fail. - **#355** — 285 routes inherit their tab title from the section above them. Breadcrumbs are derived from those same route titles, so the trail is only as accurate as the titles under it; #355 remains the fix for the labels themselves. ## Verification Each gap is covered at unit level and, where reachable without a backend, by a mocked Playwright spec. The bulk-import bug is verified by the downloaded template naming its own resource rather than the journal-entries one. -- 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]
