# Issue with enabling upcoming changes
**URL:** https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881
**Category:** Bug
**Tags:** translation, upcoming-changes
**Created:** [February 11, 2026, 6:06pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881 "2026-02-11T18:06:09Z")
**Posts on this page:** 10
**Page:** 2
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [February 24, 2026, 11:07pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/23 "2026-02-24T23:07:44Z")
Sorry for the delay, this has been merged now.
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 26, 2026, 1:11am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/24 "2026-02-26T01:11:07Z")
I just noticed there’s still a problem. When using the Edge browser on a mobile phone and the Edge browser on a computer, I set permissions so that only administrators can have access. The page displays that the setting was successful, but after refreshing, it reverts to the “Nobody” status.
---
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [February 26, 2026, 1:20am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/25 "2026-02-26T01:20:42Z")
I’m a bit confused here, if I log into your site ([https://tracker.discourse.group/](https://tracker.discourse.group/) right?) and I see the Staff option in the list, which you don’t have (or more accurately you seem to have it translated:
If I select this and reload it sticks. Am I trying it on the correct site?
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 26, 2026, 7:09am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/26 "2026-02-26T07:09:41Z")
I can repro. I think the problem is not that the staff group isn’t saved, but that after a reload it’s not shown as “selected” in the upcoming change
So I select “Team” (staff) here, then I reload, and then the interface shows “no one”. But after I select “specific groups” you can see that it was already enabled for the team group as expected. So “staff” is saved and it works for staff, but I cannot see that in the upcoming change table.
* * *
Edit:
After checking in the browser dev tools, I noticed that the JSON payload contains:
“enabled\_for”: “staff”
The dropdown value is initialized from `enabled_for`, but the “Staff” option in the select uses the actual staff group name (e.g. `"Team"`) as its value.
Since `"staff"` is not one of the dropdown option values, the select cannot match it after reload and falls back to showing “no one”.
---
### Author:  [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 26, 2026, 7:39am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/27 "2026-02-26T07:39:45Z")
I have this issue on a self-hosted VPS website, not on [https://tracker.discourse.group/](https://tracker.discourse.group/)
> [@martin](#):
>
> I’m a bit confused, if I log into your site ([https://tracker.discourse.group/](https://tracker.discourse.group/) right?) and see the “Staff” option in the list, and you don’t seem to have this option (or more accurately, you seem to have translated it):
---
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [February 27, 2026, 3:15am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/28 "2026-02-27T03:15:09Z")
Hmm okay thanks I will try reproduce again 👀
---
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [March 2, 2026, 2:43am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/29 "2026-03-02T02:43:18Z")
Okay fix is here:
[https://github.com/discourse/discourse/pull/38140](https://github.com/discourse/discourse/pull/38140)
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 1, 2026, 1:46pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/31 "2026-07-01T13:46:39Z")
I think I noticed a similar problem with the “reporting improvements” change today. I know it will be removed soon, but since I am not sure what caused it, I am reporting it anyways. Maybe it’s because it’s the only change where the dropdown offers “staff” and “custom groups” but not “everyone”? Then it might affect future changes with a similar configuration too.
```plaintext
ajax.js:233 PUT https://forum.discourse.group/admin/config/upcoming-changes/toggle 422 (Unprocessable Content)
send @ jquery.js:9940
ajax @ jquery.js:9521
i @ ajax.js:233
$ @ ajax.js:252
toggleChange @ upcoming-change-item.gjs:192
enabledForChanged @ upcoming-change-item.gjs:264
handleInput @ d-select.gjs:51
handleMouseUp_ @ (unknown)
```
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [July 1, 2026, 4:51pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/32 "2026-07-01T16:51:52Z")
Thanks @Moin - it shall soon™ be fixed
>
>
> Fixes a bug reported at https://meta.discourse.org/t/issue-with-enabling-upcomin…g-changes/395881/31
>
> \### What
>
> When an upcoming change's \`allow\_enabled\_for\` excludes \`everyone\` (for example \`\[staff, specific\_groups\]\`, as the former \`reporting\_improvements\` change had), selecting \*\*Staff\*\* in the \*Enabled for\* dropdown failed with a \`422\` and the selection snapped back to \*No one\*.
>
> \### Why
>
> \`enabledForChanged\` toggled the setting on \*\*before\*\* persisting the staff group. On the server, \`UpcomingChanges::Toggle#allowed\_enabled\_for\_target\` treats "enabled with no group configured" as targeting \`everyone\` — which these changes disallow — so the toggle was rejected and the change was never enabled.
>
> Changes that allow \`everyone\` (the common case) weren't affected, because the initial toggle passes the policy and the staff group is saved a moment later.
>
> \### Fix
>
> Persist the staff group \*\*before\*\* toggling, mirroring the existing "specific groups" path (which already saves groups first and only then enables the change). By the time the setting is toggled on, it is already scoped to staff, so the policy passes.
>
> \### Tests
>
> \- \*\*Component\*\* (\`upcoming-change-item-test.gjs\`): asserts the request order is \`groups\` → \`toggle\` for the staff selection on an \`everyone\`-excluded change, and that everyone/no-one still toggle first then clear groups.
> \- \*\*System\*\* (\`admin\_upcoming\_changes\_spec.rb\`): enabling for staff on an \`everyone\`-excluded change now succeeds and persists the staff \`SiteSettingGroup\`.
>
> \### Screenshots
>
> Before / after — selecting \*\*Staff\*\* on an \`everyone\`-excluded change (Horizon, light, desktop):
>
> \
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 1, 2026, 5:03pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/33 "2026-07-01T17:03:47Z")
Thanks, I won’t be able to confirm because the change has already been removed
[Previous page](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881.md?page=1)