mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #4766] [Feature Request]: Notes/Documentation field for Alerts #2220
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#2220
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 @entrion on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4766
Originally assigned to: @KelvinTegelaar on GitHub.
Please confirm:
Problem Statement
We can not easily add information to alerts.
Example, for the Apple alerts like expiring APN cert I have added.
Please see the following guide on handling this alert: Renew Apple MDM push certificate
Benefits for MSPs
When sending alerts we would like to add documentation, FAQ, or links on what we expect users to do with the alert.
Value or Importance
Alerts hit our service desk who are the least experienced users. They need explicit instructions on what to do.
PowerShell Commands (Optional)
No response
@kris6673 commented on GitHub (Oct 6, 2025):
This is a great idea, +1 from me on this.
Our MSP has run into the exact same troubles of the helpdesk not knowing what to do about the alerts and this would help imensely
@github-actions[bot] commented on GitHub (Oct 6, 2025):
Hello,
Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.
When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.
While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.
Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.
Thank you for understanding,
The CIPP Team
@KelvinTegelaar commented on GitHub (Oct 8, 2025):
Reopened under @kris6673
@KelvinTegelaar commented on GitHub (Oct 17, 2025):
Scripted alerts now have an option "Alert Comment" to add, this is added to each alert.