mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #3384] Halo Tenant Mapping #1554
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#1554
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 @BNWEIN on GitHub (Jan 21, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3384
Description
This used to only allow you to select tenants that had not already been mapped on the "Select Tenant" pull down. There is never a reason to map one Office 365 tenant to two customers.
It now makes it difficult to know who has been mapped and who hasnt (when you have a large data set). can this be reverted so it only shows tenants that are not already mapped please?
To replicate the issue
Have Halo Integration setup
go to CIPP > Integrations > Halo
Click on Tenant Mapping
Map a halo customer to a tenant
That tenant should no longer show on the pull down on the left (The customer should still show on the pull down on the right in case you have multiple tenants to map to a single customer)
Environment data
@github-actions[bot] commented on GitHub (Jan 21, 2025):
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!".
@BNWEIN commented on GitHub (Jan 21, 2025):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug
@BNWEIN commented on GitHub (Jan 21, 2025):
Updated this one too @KelvinTegelaar
@JohnDuprey commented on GitHub (Jan 22, 2025):
fixed in dev
@BNWEIN commented on GitHub (Feb 3, 2025):
This is still an issue i am afraid.