Aman-Mittal opened a new issue, #528: URL: https://github.com/apache/fineract-backoffice-ui/issues/528
## What happens Navigating to `/security/audit-trails` ends up on `/dashboard`. No message, no error, no indication that anything was refused or that the address was wrong: ``` requested /security/audit-trails landed on /dashboard ``` Confirmed by reading `location.pathname` after the route settles, not by eyeballing it.  The screenshot is the dashboard, because that is what the user gets. ## Why it matters Audit trails are how an institution answers "who changed this, and when" — the screen a checker, an auditor or a support engineer reaches for when something is disputed. Being quietly relocated to the dashboard is worse than a plain error, because there is nothing to act on: the user cannot tell whether - the feature does not exist in this build, - their role is missing a permission, - the URL they were given is stale, or - the page failed to load. All four look identical, and the natural response — try again — produces the same result. The signed-in user in the reproduction holds `ALL_FUNCTIONS`, so a permission gate is not the obvious explanation, though I have not ruled out a guard that resolves to a redirect regardless. ## What to look at I did not chase the cause, so this needs a look rather than a patch: - whether `/security/audit-trails` is the route the sidebar entry actually points at, or whether the entry and the route have drifted apart; - whether a route guard is redirecting rather than sending the user to the Access Denied screen the application already has for a refused route; - whether the entry should be there at all in this build. Whichever it is, the outcome should be one of: the screen, an Access Denied page, or no menu entry. A silent redirect to somewhere else is the one option that tells the user nothing. ## How to check it ``` npm start # sign in as a user with ALL_FUNCTIONS, then either # - click Audit Trails in the sidebar, or # - visit /security/audit-trails directly ``` Both land on `/dashboard`. ## Environment `main` at `55abe539`, `apache/fineract:latest` via `deploy/docker-compose-e2e.yml`, Chromium at 1440x900. Reproduced on `main` before the guided-tour branch as well, so it is not related to that work — it turned up because a tour could not be verified on a screen that never loads. -- 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]
