Suppress emails for enrollments of events

[james7342]

Is your feature request related to a problem?

Please describe.
Having used Events now for several years and haven’t figure out a way to suppress the messages sent to the event creator each time someone enrolls. Our events are not moderated and simple are a sign up to get head counts etc. Each time someone enrolls the event creator receives a message that user x has enrolled. The message for larger events and a calendar with frequent events results in excess messages to our calendar admin.

Describe the solution you'd like

A method or setting that can be selected to suppress these messages.

Describe alternatives you've considered

Make the owner of the event a specific user that just has a black hole email address. Mail box rules on the email platform.

Additional context

Maybe this is already something available in the current product and I’ve Just been unable to find it. If that is the case it’s not obvious maybe better documentation or tooltips to help provide guidance on existing feature/function/setting.

[PeterCasper]

James,
create a new email address. I like gmail for black holes, outlook for novice users or yandex for groups with a registered domain name but no money.
Send your email to your new black hole. If you set it up correctly so that it emails then no email failure message is received by DNN and you have an audit trail if required.
You might consider flushing out the old emails every decade or so. No rush.
Peter

[james7342]

That was the exact thought I had as a quick workaround. Just thought it would be nice to have an official way to suppress the messages if one wanted.

[stale]

We have detected this issue has not had any activity during the last 180 days.
That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue.
We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future.
Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all.
Thank you for your continued involvement and contributions!

[james7342]

Not sure this be closed out. I still think this would be a nice feature just don't have the expertise to do it myself in the spirit of open source.

[stale]

We have detected this issue has not had any activity during the last 180 days.
That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue.
We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future.
Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all.
Thank you for your continued involvement and contributions!

[james7342]

Still think this would be a nice feature.

[stale]

We have detected this issue has not had any activity during the last 180 days.
That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue.
We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future.
Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all.
Thank you for your continued involvement and contributions!

[james7342]

Is there anyway to make this a feature request and not have stale bot try and close it?

[james7342]

Never mind. It's already tagged as an enhancement.

[WillStrohl]

Hello @james7342: The stalebot feature is just an automated way to help do some of the backlog grooming for the project. Since this is an open-source software solution, it's updates are all dependent on volunteers and sponsored development. With this being the case, the stalebot feature is a great way to save management time for issues that may grow to truly be "stale" over time. It also helps to prevent wasted time on issues that truly no longer relevant.

Stale: It doesn't mean the issue is unimportant for you. If you respond, it simply confirms that the issue is not stale and still important. Your reply is all that is needed.

Relevant: Relevance when it comes to a software solution like this has many definitions, but the two primary ones are (1) the issue is still occurring (sometimes stuff is fixed by other updates); and (2) the update still can and should be done even though time has passed and it may not be a relevant update anymore (e.g., other means and/or perspective have changed since the issue was reported).

I hope this helps to give more background about this feature. I know that the first time you see it, it could feel off-putting. 😉

[WillStrohl]

I didn't mean to close this issue on you. I think I accidentally found a new hotkey when I submitted my reply a moment ago. Sorry! 🤦🏽‍♂️ 😄

[james7342]

@WillStrohl No problem. I get the idea and have ran into stale bot in other projects. I was just thinking if there was a way for a feature/enhancement request to not be flagged stale until possibly some decision had been made by the project owner/team. IE: Introduce/Reject. I do agree though even though It's important feature to me doesn't mean it's important to the larger community. Stale Bot for defects I would agree as it might not be relevant anymore in later releases and/or as it's been fixed via some code changes/fix. Thank you for the information.

[stale]

We have detected this issue has not had any activity during the last 180 days.
That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue.
We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future.
Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all.
Thank you for your continued involvement and contributions!

[stale]

This issue has been closed automatically due to inactivity (as mentioned 21 days ago).
Feel free to re-open the issue if you believe it is still relevant.