Skip to content

ref(flags): Unregister organizations:issue-stream-recommended-sort - #127210

Merged
roggenkemper merged 1 commit into
masterfrom
claude-rm-issue-stream-recommended-sort-registration
Oct 14, 2026
Merged

roggenkemper merged 1 commit into
masterfrom
claude-rm-issue-stream-recommended-sort-registration

Conversation

@cursor

@cursor cursor Bot commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Remove the registration of organizations:issue-stream-recommended-sort from temporary.py. This flag was fully rolled out in the automator in PR #8428 on 6/30/26 (GA segment, rollout: 100, conditions: []) and hasn't been touched since.

Step 3 of 3, merge last: the frontend reads are removed by #127209 and the automator value by getsentry/sentry-options-automator#10141. Merging this before those land would make organization.features drop the flag while the UI still reads it, hiding the Recommended sort option until #127209 deploys.

The ...-default and ...-experimental siblings are separate, still-live flags and stay registered.

Open in Web View Automation 

The flag reached GA (rollout 100%, no conditions) in sentry-options-automator
#8428 on 2026-06-30. Reads are removed by #127209 and the automator value by
sentry-options-automator#10141; merge this last.

The -default and -experimental siblings stay registered.

Co-authored-by: charlie.luo <charlie.luo@sentry.io>
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 12, 2026
@cursor
cursor Bot marked this pull request as ready for review October 12, 2026 20:51

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@getsentry/issue-detection-backend @getsentry/app-backend @getsentry/issues-feed — last of 3 PRs cleaning up organizations:issue-stream-recommended-sort (flagpole owner.team: issue_detection; src/sentry/features/ has no CODEOWNERS entry, hence @getsentry/app-backend).

Merge order — this one goes last:

  1. #127209 — removes the two frontend reads
  2. getsentry/sentry-options-automator#10141 — removes the flagpole value
  3. this PR — removes the registration

Merging this first wouldn't break CI (the flag's only readers were frontend organization.features.includes(...), which can't raise Unregistered feature flag), but api_expose=True means the org serializer would stop emitting the flag while the UI still reads it — the Recommended sort option would disappear until #127209 deploys.

The ...-sort-default and ...-sort-experimental siblings stay registered; they're separate flags with their own live readers.

CI: 69 green, 1 red — the red is the usual getsentry dispatch gate, which fails because the author (cursor[bot]) has no write permission. A collaborator needs to add the Trigger: getsentry tests label.

View PR

Open in Web View Automation 

Sent by Cursor Automation: Feature flag cleanup

@roggenkemper roggenkemper added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Oct 14, 2026
@roggenkemper
roggenkemper merged commit fd07b5f into master Oct 14, 2026
123 of 124 checks passed
@roggenkemper
roggenkemper deleted the claude-rm-issue-stream-recommended-sort-registration branch October 14, 2026 18:48
adrianviquez pushed a commit that referenced this pull request Oct 14, 2026
…127210)

Remove the registration of `organizations:issue-stream-recommended-sort`
from `temporary.py`. This flag was fully rolled out in the automator in
PR #8428 on 6/30/26 (GA segment, `rollout: 100`, `conditions: []`) and
hasn't been touched since.

Step 3 of 3, **merge last**: the frontend reads are removed by #127209
and the automator value by getsentry/sentry-options-automator#10141.
Merging this before those land would make `organization.features` drop
the flag while the UI still reads it, hiding the Recommended sort option
until #127209 deploys.

The `...-default` and `...-experimental` siblings are separate,
still-live flags and stay registered.

<div><a
href="https://cursor.com/agents/bc-0022944d-a6ae-4bd6-b615-0fa636824997?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/automations/b02055f4-b602-11f1-bb68-864e54d14197"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/view-automation-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/view-automation-light.png"><img
alt="View Automation" width="141" height="28"
src="https://cursor.com/assets/images/view-automation-dark.png"></picture></a>&nbsp;</div>

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: charlie.luo <charlie.luo@sentry.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants