mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2137] displayName and description not honored for Intune Device/Catalog templates #1095
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#1095
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 @DanielWahlgren on GitHub (Feb 20, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2137
Description
In Modules/CIPPCore/Public/Entrypoints/Invoke-AddPolicy.ps1
For Admin, it replaces the displayName and description with the information provided in the UI, but for Device- and Catalog-templates it does not. This is confusing, especially when trying to add the same policy twice. Changeing the name will give the errormessage that the new name already exist, but in reality, it's the original name that already exist, so the errormessage becomes missleading.
So more like this, except tested :)
Environment data
@github-actions[bot] commented on GitHub (Feb 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!".
@KelvinTegelaar commented on GitHub (Feb 20, 2024):
Already fixed in dev
@DanielWahlgren commented on GitHub (Feb 20, 2024):
Thank you Kevin!