mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #3621] [Bug]: Domains Analyser checkboxes #1608
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#1608
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 @bitjbullock on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3621
Required confirmations before submitting
Issue Description
When trying to remove onmicrosoft.com domains from the Domain Analyser report list, we noticed that sometimes it would delete domains we had not selected. I was able to replicate this 3 separate times, and then of course realised I couldn't add the domain back in after my testing. oops.
Steps to reproduce:
I suspect that what's happening is the check box is associated with "Line X of chart" but then as you create filters, the line number changes that is associated with the domain the user is trying to select, so the back end ends up picking Line 4 as an example and line 4 is associated with contoso.com and the user sees line 4 associated with contoso.onmicrosoft.com and then inadvertently deletes a domain from the analyser that is needed.
I'll submit a secondary feature request but this brings up a good point, if you delete a domain from the domain analyser, there should be a way to add it back in.
Environment Type
Non-sponsored user
Front End Version
7.1.3
Back End Version
7.1.3
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Feb 12, 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!
@KelvinTegelaar commented on GitHub (Feb 13, 2025):
Fixed in dev