[GH-ISSUE #1391] Unable to set up Alerts Wizard on current dev version #773

Closed
opened 2026-03-02 12:45:05 +03:00 by kerem · 3 comments
Owner

Originally created by @BNWEIN on GitHub (Feb 23, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1391

Description

Just letting you know before the next update. This is not actually causing me any issues, but in the current Dev version you are unable to setup alerts. When you go to the Alerts Wizard, select a customer, and try and click "Next" you get an error at the bottom of the page that simple says "Required"

Environment data

Dev Environment
Local
Originally created by @BNWEIN on GitHub (Feb 23, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1391 ### Description Just letting you know before the next update. This is not actually causing me any issues, but in the current Dev version you are unable to setup alerts. When you go to the Alerts Wizard, select a customer, and try and click "Next" you get an error at the bottom of the page that simple says "Required" ### Environment data ```PowerShell Dev Environment Local ```
kerem 2026-03-02 12:45:05 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 23, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1441984237 --> @github-actions[bot] commented on GitHub (Feb 23, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@BNWEIN commented on GitHub (Feb 23, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:1441984696 --> @BNWEIN commented on GitHub (Feb 23, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@KelvinTegelaar commented on GitHub (Feb 27, 2023):

Fixed in dev

<!-- gh-comment-id:1446119317 --> @KelvinTegelaar commented on GitHub (Feb 27, 2023): Fixed in dev
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#773
No description provided.