mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2407] [HaloPSA Extension] Auto-Mapping Duplicates Mappings #1223
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#1223
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 @martinyelland on GitHub (May 3, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2407
Description
When the Auto-Mapping Feature is used, it creates the mappings in the table - but it does not first check if the mapping already exists.
Expected Outcome:
CIPP ignores the existing mappings where identical
CIPP updates an existing mapping, where a tenant is assigned to different Client Name.
CIPP does not duplicate the existing mappings, or allow duplicates to be committed.
Actual Outcome:
New Mappings are added
All existing mappings are duplicated in the UI and the Table when saved.
Steps to Reproduce:
Environment data
@github-actions[bot] commented on GitHub (May 3, 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 (May 3, 2024):
combing this with your feature request and reopening that one :)