mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2237] Can't add policy template #1153
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#1153
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 @easywaveio on GitHub (Mar 20, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2237
Description
I have one policy that I can't add to templates anymore. I have tried by manually import the JSON and via "Create template based on policy" button in CIPP.
This policy worked as a template before, but after adding some extra settings from the "settings catalog" I can't get it to import into policy templates in CIPP anymore. Other policies still works fine, so there have to be one setting that breaks this one. I have tried to remove my last changes but still no go.
I have attached the JSON, with all the settings as they should be.
EW_ Hardening_2024-03-20T16_27_48.967Z.json
Environment data
@github-actions[bot] commented on GitHub (Mar 20, 2024):
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://docs.cipp.app/
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!".
@easywaveio commented on GitHub (Mar 20, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Mar 20, 2024):
This is a support issue, not a bug. Please contact the helpdesk for support issues.