feat(issues): Add recommended sort with localStorage persistence#116320
Merged
roggenkemper merged 7 commits intoJun 18, 2026
Conversation
Gate the experimental recommended sort behind the issue-stream-recommended-sort feature flag. Also show the option when ?sort=recommended is already in the URL for manual testing. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
When the issue-stream-recommended-sort flag is enabled, default the sort to "recommended" instead of "last seen". Persist the user's sort choice in localStorage so it survives navigation. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff
🔍 4 new type safety issues introducedType assertions (
This is informational only and does not block the PR. |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
scttcper
approved these changes
Jun 16, 2026
…is enabled onSortChange wrote the selected sort to localStorage unconditionally, but the default sort only reads that stored value when the issue-stream-recommended-sort flag is on. A user who changed sort before getting the flag would have a stale value persisted, and once the flag turned on it would override the intended Recommended default. Gate the write on the same flag as the read so the conditions stay symmetric. Co-Authored-By: Claude <noreply@anthropic.com>
sehr-m
pushed a commit
that referenced
this pull request
Jun 23, 2026
…6320) Add the experimental "Recommended" sort option to the issue stream dropdown, gated behind the `issue-stream-recommended-sort` feature flag. Users with the flag see "Recommended" as their default sort, which ranks issues by combined recency, severity, and impact signals (backend in #111043). Sort selection is persisted in localStorage per-org so the choice survives page navigation. The sort also appears in the dropdown when `?sort=recommended` is in the URL, allowing manual testing without the flag. The `?sort=recommended` query param fallback was included so anyone can test the sort without needing the feature flag enabled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the experimental "Recommended" sort option to the issue stream dropdown,
gated behind the
issue-stream-recommended-sortfeature flag. Users withthe flag see "Recommended" as their default sort, which ranks issues by
combined recency, severity, and impact signals (backend in #111043).
Sort selection is persisted in localStorage per-org so the choice survives
page navigation. The sort also appears in the dropdown when
?sort=recommendedis in the URL, allowing manual testing without the flag.
The
?sort=recommendedquery param fallback was included so anyone can testthe sort without needing the feature flag enabled.