# The prompt message given when upcoming changes are officially added is not clear enough
**URL:** https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676
**Category:** UX
**Tags:** upcoming-changes
**Created:** [2 juli 2026 om 17:23 UTC](https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676 "2026-07-02T17:23:30Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Noble\_Fish](https://meta.discourse.org/u/Noble_Fish)
#### Post date: [2 juli 2026 om 17:23 UTC](https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676/1 "2026-07-02T17:23:30Z")
The prompt message given when upcoming changes are officially added is not clear enough.
The wording here says that a certain setting item has been automatically enabled, but clicking on it will navigate to the upcoming changes page, where that setting item no longer exists; after clicking it, the user is taken to the admin page, but is not guided to the setting item to turn this change off or on.
This may cause some misunderstandings.
---
### Author:  [@Noble\_Fish](https://meta.discourse.org/u/Noble_Fish)
#### Post date: [2 juli 2026 om 17:26 UTC](https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676/2 "2026-07-02T17:26:35Z")
For example, I now feel a bit confused: why call it “automatically enabled” rather than “xxx change is now a fixed behavior”? After all, clicking on this prompt that says “has been automatically enabled” does not lead the user to the setting item to turn it off. Also, since I wasn’t led to a toggle, why did clicking this message take me to the admin page…?
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [2 juli 2026 om 20:35 UTC](https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676/3 "2026-07-02T20:35:45Z")
> [@Noble\_Fish](#):
>
> I now feel a bit confused: why call it “automatically enabled” rather than “xxx change is now a fixed behavior”?
I think this happened because the step where this would usually have been enabled was skipped.
But I also wondered about the change not being visible today
> [@Introducing Upcoming Changes, a system to manage new features and changes to existing functionality in your community](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/39):
>
> I also tried to look at how it works now, but I can’t find the change. Does anyone have an idea what I’m doing wrong? The version is [08cf6f4](https://github.com/discourse/discourse/commits/08cf6f4574b893caecda402545f98becad1ac2da)
>
> 
I was especially interested in this because I had asked about the [purpose of the “permanent” status filter](https://meta.discourse.org/t/what-is-the-purpose-of-the-permanent-filter-on-the-upcoming-changes-page/402433/2) before, and thought I could finally try it because there is a change in this state now, but there is still no result so it didn’t help me to understand.
---
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [3 juli 2026 om 06:43 UTC](https://meta.discourse.org/t/the-prompt-message-given-when-upcoming-changes-are-officially-added-is-not-clear-enough/406676/4 "2026-07-03T06:43:58Z")
Skipping to Permanent doesn’t usually happen so it exposed a bug with the notification link in this case, which was fixed here:
>
>
> When an upcoming change was automatically enabled, the notification
> linked admi…ns to the upcoming changes config page. But once a change
> reaches permanent status it no longer appears there (that page only
> lists experimental through stable) and instead surfaces on the What's
> New page. So if the notification was left unread until the change became
> permanent, clicking it dropped the admin on an empty filtered list.
>
> This resolves the change's status at click time rather than baking it
> into the notification. The permanent change names are now exposed to
> staff via the site serializer, and the notification's link checks them:
> if every referenced change is now permanent, it sends the admin to
> What's New scrolled to that change's card; otherwise it keeps the
> existing upcoming changes page where the still non-permanent changes
> remain actionable.
>
> To support the scroll, every What's New item now has a stable id anchor,
> and the page accepts a scrollTo query param that scrolls to and briefly
> highlights the matching card once the feed loads.
>
> \
>
> \
Also, Permanent changes show in the `/admin/whats-new` page which I mentioned in [Introducing Upcoming Changes, a system to manage new features and changes to existing functionality in your community - #41 by martin](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/41) earlier, and I’ve now added to the OP of that topic.