Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled Task Notifications sent to all users with "receive system emails" on #39311

Open
crystalenka opened this issue Nov 25, 2022 · 9 comments

Comments

@crystalenka
Copy link
Member

Steps to reproduce the issue

  1. Create several users from various user groups. Make sure "receive system emails" is on and that the user groups do not have access to the scheduled tasks component.
  2. Create a scheduled task.
  3. Set all task notifications to on.
  4. Trigger the task.

Expected result

Only users with permissions to access the scheduled task component receive the notification email.

Actual result

All users with 'receive system emails' turned on receive notifications, regardless of permissions.

System information (as much as possible)

PHP 8.1, J4.2.5

Additional comments

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.

@brianteeman
Copy link
Contributor

The same fundamental issues with task notifications are present with workflow notifications

#37746, #37745, #37743, #37422

@brianteeman
Copy link
Contributor

are you offering to help or are you going to keep commenting from the sidelines and telling everyone else what to do

@ReLater
Copy link
Contributor

ReLater commented Nov 25, 2022

Whats wrong in commenting for the sake of commenting?

  1. This is not a forum, but an issue tracker.
  2. It does not help anyone.
  3. Volunteers work when they want to, can and have time.

@wojtekxtx , get started!

@alikon
Copy link
Contributor

alikon commented Nov 25, 2022

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

@crystalenka
Copy link
Member Author

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.

@crystalenka
Copy link
Member Author

Also it's less about how you personally use it and more about "Joomla offers this feature therefore it should work well in core".

@chmst
Copy link
Contributor

chmst commented Nov 25, 2022

get emails from failed scheduled tasks even though they have no access to even see the component.

Did you check the users permissions in the permissions view? Like that?

grafik

Maybe the user don't see the component in the menu, but have full manager permission. Then the condition
would be true.

@crystalenka
Copy link
Member Author

So here's an interesting discrepancy.

Component settings are all denied, but task settings apparently don't inherit from the component settings?

Screenshot 2022-11-25 at 23 15 39

Screenshot 2022-11-25 at 23 17 09

@chmst
Copy link
Contributor

chmst commented Nov 25, 2022

I am not sure, but there could be a reason for these notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants