discourse/spec/services/upcoming_changes
Martin Brennan dcf6da9cef
UX: Allow more specific enabled for options for upcoming changes (#39916)
Certain upcoming changes do not make sense to enable for "Everyone",
like changes that will only affect the admin UI. We currently have
a disallow_enabled_for_groups option that changes the "Enabled for"
dropdown to only show Everyone and No one, but this is a bit of a blunt
instrument.

This change adds an `allow_enabled_for` option for upcoming changes
which is a YAML array:

* When omitted, the "Enabled for" dropdown will show Everyone, Staff,
Specific group(s) and No one.
* When set to everyone, the dropdown will only show Everyone and No one.
* When set to staff, the dropdown will only show Staff and No one.
* It can also be set to staff and specific_groups

This commit also changes the reporting_improvements upcoming change
to be staff, specific_groups and adds a DB migration to account for
this.
2026-05-13 10:22:06 +10:00
..
action PERF: Cache has_unseen_features? to avoid per-request git shell-outs (#39532) 2026-04-24 10:16:46 -07:00
list_spec.rb DEV: Conditional display of upcoming changes (#39915) 2026-05-12 16:02:55 +10:00
notify_promotion_spec.rb DEV: Fix upcoming change notification flaky specs (#38914) 2026-03-27 15:03:23 +08:00
notify_promotions_spec.rb DEV: Fix upcoming change notification flaky specs (#38914) 2026-03-27 15:03:23 +08:00
toggle_spec.rb UX: Allow more specific enabled for options for upcoming changes (#39916) 2026-05-13 10:22:06 +10:00
track_spec.rb FIX: Do not notify admins of upcoming changes on new sites (#38890) 2026-03-27 12:32:12 +10:00