Skip to content

Conversation

@cteyton
Copy link
Contributor

@cteyton cteyton commented Feb 9, 2026

Summary

The filter dropdowns (Repository, Evaluator) in the Issues page were sorting values using JavaScript's default .sort(), which performs case-sensitive comparison. This caused uppercase entries (e.g., "PostHog/posthog") to appear before lowercase ones (e.g., "bigint/hey"), resulting in an unintuitive ordering for users.

Changes

  • File: src/api/routes/issues.ts
  • Replaced .sort() with .sort((a, b) => a.localeCompare(b, undefined, { sensitivity: "base" })) for both evaluators and repositories filter arrays
  • This applies case-insensitive locale-aware sorting, so entries like "bigint/hey" and "Checkmk/checkmk" are interleaved alphabetically regardless of casing

Why

The previous case-sensitive sort grouped all uppercase-starting names before lowercase ones, making it harder for users to find repositories and evaluators in the filter dropdowns. Case-insensitive sorting matches user expectations for alphabetical lists.

Implementation details

  • The fix is backend-only — the frontend already renders filter values in the order received from the API
  • Uses localeCompare with sensitivity: "base" which ignores both case and diacritics for sorting
  • Hardcoded filters (Severity: High/Medium/Low, Issue Type: Errors/Suggestions) were already in logical order and required no changes

This PR was written using Vibe Kanban

The filter dropdowns (Repository, Evaluator) used default .sort() which
is case-sensitive, putting uppercase entries before lowercase ones.
Switch to localeCompare with sensitivity: "base" for proper
case-insensitive alphabetical ordering.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@cteyton cteyton merged commit b29a80a into main Feb 9, 2026
3 checks passed
@cteyton cteyton changed the title In the "Issues" page, the values in each filter component must be sorted by alphabetical order. (vibe-kanban) Fix case-sensitive sorting of filter values in Issues page (Vibe Kanban) Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant