Invalid Query Parameters Reload Page with No Validation

Current Behaviour: Currently, when a user manually modifies the query parameters in the URL (e.g., state_group), the system reloads the page even if the entered value doesn't match any valid filter or state group. This results in unnecessary page reloads and a confusing user experience.

Expected Behaviour: When a user enters an invalid or non-existing state group in the query parameters, the system should Validate the query parameter against predefined state groups. If invalid, show a custom error message like "Filter not found" or "Invalid state group."Alternatively, fallback to a default or existing valid state group instead of reloading the page.

Steps to Reproduce:

1. Go to the issue tracking page.
2. Manually modify the URL query parameter for state_group to an invalid value (e.g., state_group=hello when "hello" is not a valid state group).
3. Observe that the page reloads with a generic "No issues yet" message.
   Actual Result: The page reloads with a generic message, even though the issue is with an invalid filter.

Start at the issue tracking page and reproduce the behavior with an invalid state_group query parameter such as state_group=hello. Trace the query-parameter handling and predefined state groups, then verify that invalid values produce a clear validation result or use a valid fallback instead of showing a misleading empty state.