/app/ticketing/settings returns 404 (route ordering bug) #2

New Issue

jwed · 2026-04-09T21:28:17-07:00

jwed commented

2026-04-09 21:28:17 -07:00

Steps to Reproduce

Log in
Navigate to /app/ticketing/settings

Expected

Settings page loads (200)

Actual

HTTP 404 — the /{ticket} wildcard route captures /settings as a ticket ID before the settings route can match

Root Cause

In src/routes/ticketing.php the settings routes are registered inside a permission:ticketing.settings group, but Laravel evaluates routes in declaration order. The GET /{ticket} wildcard (registered earlier in a different group) matches /settings first, looks for a ticket with ID/slug "settings", finds nothing, and returns 404.

Fix

Register all specific paths (/settings, /create) before the /{ticket} wildcard route.

Found by QA runner — happy-path suite

## Steps to Reproduce 1. Log in 2. Navigate to `/app/ticketing/settings` ## Expected Settings page loads (200) ## Actual HTTP 404 — the `/{ticket}` wildcard route captures `/settings` as a ticket ID before the settings route can match ## Root Cause In `src/routes/ticketing.php` the settings routes are registered inside a `permission:ticketing.settings` group, but Laravel evaluates routes in declaration order. The `GET /{ticket}` wildcard (registered earlier in a different group) matches `/settings` first, looks for a ticket with ID/slug "settings", finds nothing, and returns 404. ## Fix Register all specific paths (`/settings`, `/create`) before the `/{ticket}` wildcard route. *Found by QA runner — happy-path suite*

jwed referenced this issue from a commit

2026-04-09 21:31:52 -07:00

fix: move /settings route before /{ticket} wildcard; fix null tickets on bootstrap

jwed closed this issue

2026-04-09 21:31:52 -07:00

jwed referenced this issue from a commit

2026-04-09 21:33:48 -07:00

fix: replace role check with permission check in TicketingSettingsController

Sign in to join this conversation.