-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix #14379: Provided options in multiselect fields consolidate users, segments, etc. with same name #14794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Appends the object ID in brackets after the name to ensure clarity. Applied changes across multiple areas: Segments, Campaigns and others. Add new acceptance Test for Multiselect Field Fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no suggestions here. Really nicely done, nice E2E tests added. 👍
Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome. The code changes look good to me.
@all-contributors please add @1792826181 for code |
I've put up a pull request to add @1792826181! 🎉 |
Just had a confusion on this when testing where someone thought the number was the number of contacts in a segment (we have fairly large ID in the hundreds). I’ll see if any other reports but wanted to note as it could be worth having it say (ID: x) instead? |
@driskell I like that! Just a number without any unit is confusing. But it's already in other places so we should change it at all places. |
Description
When multiple objects share the same name in the multiselect fields only one of them would be displayed, making it difficult to select the correct object. This issue affected segments, campaigns, categories, and other entities, leading to user confusion and selection errors.
The problem was caused by the way object lists were indexed using names as keys, which led to duplicate entries being overwritten. To fix this, the logic was updated to append each object's unique ID in parentheses, ensuring clear differentiation. The changes were applied consistently across all affected areas and tests were created to verify that the objects are now properly distinguishable.
📋 Steps to test this PR: