Issue Bug Closed

#76224State change notifications not send when option „Notify all users on any change“ is not set (workspaces)

Christian Richter 05/18/16, 13:55 updated 08/12/25, 14:35

Description

When a user sends a change to another stage, a notification mail only gets send when the change is moved to the LIVE-Workspace.

Our Setup:

One additional Workspace that we call “PREVIEW Workspace“
Some BE Users are Owners in the User-Tab, some BE Users are Members in the User-Tab.

We have three stages editing, ready to publish and publishing execute.
By default, only if a change is moved to publishing execute a notification mail get’s send.
I can check and uncheck the respective Owners and Members on each stagechange, but no mail gets send.
If I enable the option „Notify all users on any change“ I can check and uncheck Owners and Members on each stage-change and the respective notification-mails are send.
Only checked Users are getting notifications, no matter which status they have (Member/Owner).

So from my point of view everything is working fine when „Notify all users on any change“ is set, but the name of the option made me think that indeed ALL USERS are notified on ANY CHANGE without respecting my manual restrictions/selections.

Reviews 2

Files 3

History 810

  1. Oliver Hader commented <span data-processor="relativetime" data-value="2016-05-18T14:39:10+00:00" > 05/18/16, 14:39 </span>

    Can you please add a screenshot of the relevant configuration of the workspace record? This way it’s easier to ensure we’re talking about the same behavior. Thanks in advance…

  2. Christian Richter changed attached workspace_users.png attached option_set.png attached checkboxes.png <span data-processor="relativetime" data-value="2016-05-18T14:53:20+00:00" > 05/18/16, 14:53 </span>

  3. Rémy DANIEL commented <span data-processor="relativetime" data-value="2020-05-06T18:40:29+00:00" > 05/06/20, 18:40 </span>

    Christian, do you have a better label for the option „Notify all users on any change“?

  4. Benni Mack commented <span data-processor="relativetime" data-value="2025-06-23T21:46:58+00:00" > 06/23/25, 21:46 </span>

    Since #90411 the field “stagechg_notification” does not make a difference between value “1” and “10”. So we should evaluate if we just make a checkbox out of the field.

  5. Christian Kuhn commented <span data-processor="relativetime" data-value="2025-07-11T10:55:57+00:00" > 07/11/25, 10:55 </span>

    agreed benni. i came across this select box as well. will push a change.

  6. Christian Kuhn commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-07-11T16:40:10+00:00" > 07/11/25, 16:40 </span>

    Applied in changeset commit:7979620cac9d14c16e2a0ba859ed6402b9ee40e2.