Only users with permissions to access the scheduled task component receive the notification email.
All users with 'receive system emails' turned on receive notifications, regardless of permissions.
PHP 8.1, J4.2.5
Ideal solution would be to define which user groups get notified on a per-task level, maybe in the task permissions (because different people may need to handle different errors).
Otherwise, either via component permissions or by selecting user groups in component options.
Default should be super users only.
Labels |
Added:
No Code Attached Yet
|
@brianteeman that means its not one-off
case. So it needs to be worked on ASAP
are you offering to help or are you going to keep commenting from the sidelines and telling everyone else what to do
@brianteeman are you asking or are you stating the fact?
BTW: Whats wrong in commenting for the sake of commenting? I seriously fail to see whats wrong with it.
Whats wrong in commenting for the sake of commenting?
@wojtekxtx , get started!
as I believe that I'm one of the few that use scheduled tasks, heavily on the wild,
I always Set:
all task notifications to off...
cause , there are far more better tools to be notified
so can you clarify a little bit better your use case ?
cause to me this is not a bug
is a nice to have
I use scheduled tasks for a few things on my client sites. Since I manage quite a few of them, and some of these scheduled tasks are site-specific, I like it when it lets me know when there is a failure.
However, as they are client sites, they also have user accounts. Most do not have or need system notifications on. Some have apparently accidentally turned it on and now get emails from failed scheduled tasks even though they have no access to even see the component.
This is not a nice to have, this is a flaw with how the system is set up. People who cannot see scheduled tasks should not be able to get notifications about them.
Also it's less about how you personally use it and more about "Joomla offers this feature therefore it should work well in core".
I am not sure, but there could be a reason for these notifications.
Labels |
Added:
bug
|
Labels |
Added:
?
Removed: bug |
The same fundamental issues with task notifications are present with workflow notifications
#37746, #37745, #37743, #37422