mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-26 00:36:27 +03:00
[GH-ISSUE #1258] [Feature Request]: Scheduled Alerts split by customer #702
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#702
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BNWEIN on GitHub (Dec 13, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1258
Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.
Currently with the Scheduled Alerts, the email will come with alerts from any/all customers you have alerts setup for.
To better integrate these alerts with a ticket system (as an example) it would be great if the alerts could be split per customer. IE
1 Email for customer A detailing all scheduled alerts for that customer
1 Email for customer B detailing all scheduled alerts for that customer.
1 Email for customer C detailing all scheduled alerts for that customer.
Ideally the email alert should of course include the customer tenant name/default domain or other easily identifiable information. That can be used with automation rules within a ticket system to log a ticket directly under the relevant customer.
I think this would benefit all MSP's who are using the scheduled alerts to log tickets in their ticketing platform.
PowerShell commands you would normally use to achieve above request
No response
@github-actions[bot] commented on GitHub (Dec 13, 2022):
Thank you for creating a feature request!
Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR.
If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority".
If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will.
If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".
@BNWEIN commented on GitHub (Dec 13, 2022):
I would like to upgrade the priority
@KelvinTegelaar commented on GitHub (Dec 16, 2022):
added checkbox to allow splitting at notification config.