Issue with enabling upcoming changes

martin · February 13, 2026, 5:26am

Thanks for the reproduction Moin, I wasn’t aware that automatic group names could be changed in this way. Fix is here:

github.com/discourse/discourse

FIX: Staff group causing errors in upcoming changes from localization (#37797)

main ← issue/uc-staff-localization-group

merged 11:07PM - 24 Feb 26 UTC

martin-brennan

+66 -16

We have a "Staff" option for upcoming change items that was sending the `staff`… group name to the server. I had assumed that our automatic groups could not be renamed, but this is not the case. If your `default_locale` for your site is changed, the automatic group names change via `Group.refresh_automatic_groups!` in a background job. This means that if you change your `default_locale` to `de` (German), the `staff` group becomes `Team`, and the upcoming changes that are set to "Staff" will now be looking for the `staff` group, which no longer exists, causing errors. This commit fixes the issue by always using the localized staff automatic group name, both for the value of the dropdown, and in successs messsages etc. c.f. https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/16

Topic		Replies	Views
Non-English Group name cause Error 500 for group message Support	11	885	May 24, 2021
Introducing Upcoming Changes, a system to manage new features and changes to existing functionality in your community Announcements	16	623	February 24, 2026
Upcoming Changes Site Management	0	85	February 10, 2026
/groups/AD1 won't work (too short?) Bug	4	729	October 17, 2016
Adding owners/members UX is inconsistent and misleading UX	26	3047	April 20, 2018

Issue with enabling upcoming changes

Related topics