Redirect single-result admin user searches to the edit page #1010

New issue

Closed

opened 2026-11-05 10:31:25 -06:00 by Codex · 2 comments

Codex commented

2026-11-05 10:31:25 -06:00

Member

The /admin/users search should reduce unnecessary navigation when exactly one matching account exists.

The existing admin user flow is defined in the web routes and must retain its current authorization and mutation protections.

Scope

Update the /admin/users search handling in routes/web.php and its existing controller/view implementation to redirect exactly one match to that user’s edit page.
Keep zero-result and multiple-result searches on the existing results flow.
Preserve existing admin role checks, validation, pagination, and named rate limiting.

Acceptance Criteria

A search producing exactly one user redirects directly to that user’s existing edit page.
A search producing zero users continues to show the existing empty-results state.
A search producing multiple users continues to show the existing results list.
The redirect uses the existing user identifier and edit route, without exposing users outside the existing administrative authorization rules.

Test Coverage Required

Add feature coverage for zero, one, and multiple matching users through the /admin/users search endpoint.
Assert that the single-match response redirects to the existing edit-user route and identifies the matched account.
Assert that zero- and multiple-match responses retain the existing results behavior.

Progress Checklist

Locate the existing /admin/users search route, handler, results query, and edit route.
Implement the single-result redirect while preserving existing authorization and request protections.
Add focused feature tests for each result-count branch.
Run the repository’s prescribed focused feature test and formatting checks.

The `/admin/users` search should reduce unnecessary navigation when exactly one matching account exists. The existing admin user flow is defined in the web routes and must retain its current authorization and mutation protections. ## Scope - Update the `/admin/users` search handling in `routes/web.php` and its existing controller/view implementation to redirect exactly one match to that user’s edit page. - Keep zero-result and multiple-result searches on the existing results flow. - Preserve existing admin role checks, validation, pagination, and named rate limiting. ## Acceptance Criteria - A search producing exactly one user redirects directly to that user’s existing edit page. - A search producing zero users continues to show the existing empty-results state. - A search producing multiple users continues to show the existing results list. - The redirect uses the existing user identifier and edit route, without exposing users outside the existing administrative authorization rules. ## Test Coverage Required - Add feature coverage for zero, one, and multiple matching users through the `/admin/users` search endpoint. - Assert that the single-match response redirects to the existing edit-user route and identifies the matched account. - Assert that zero- and multiple-match responses retain the existing results behavior. ## Progress Checklist - [x] Locate the existing `/admin/users` search route, handler, results query, and edit route. - [x] Implement the single-result redirect while preserving existing authorization and request protections. - [x] Add focused feature tests for each result-count branch. - [x] Run the repository’s prescribed focused feature test and formatting checks.

Codex added the

Rows
Columns