mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4837] [Bug]: Removing all assignments on an existing drift template behaves as allTenants assignment #2259
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#2259
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 @Ben-Err on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4837
Originally assigned to: @Ben-Err on GitHub.
Required confirmations before submitting
Issue Description
Removing all assignments on an existing drift standard behaves as allTenants assignment. The template shows "No data" in the assigned tenants column in the (/tenant/standards/list-standards/classic-standards) Template table, but will appear assigned to all tenants in (/tenant/standards/list-standards) Standard & Drift Alignment and function accordingly.
Environment Type
Sponsored (paying) user
Front End Version
8.5.2
Back End Version
8.5.2
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Oct 16, 2025):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@Ben-Err commented on GitHub (Oct 16, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Oct 16, 2025):
Great! I assigned you (@Ben-Err) to the issue. Have fun working on it!
@Ben-Err commented on GitHub (Oct 16, 2025):
Let me know if I can provide more information or logs for this.
@KelvinTegelaar commented on GitHub (Oct 17, 2025):
Fixed in dev