fix(SO): search options not working with default values in multi-select#980
Merged
Conversation
MyvTsv
requested review from
Rom1-B and
stonebuzz
and removed request for
stonebuzz
stonebuzz
approved these changes
Jul 17, 2025
Contributor
|
@MyvTsv can you valide with customer? |
Rom1-B
requested changes
Jul 23, 2025
Contributor
Rom1-B
left a comment
Rom1-B
left a comment
There was a problem hiding this comment.
Seems OK
Waiting customer validation.
Contributor
Author
|
It's good for the customer |
Rom1-B
approved these changes
Jul 30, 2025
Contributor
Rom1-B
left a comment
Rom1-B
left a comment
There was a problem hiding this comment.
Please rebase to solve conflicts
Rom1-B
approved these changes
Aug 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
When a multiple drop-down list field, defined via the Fields plugin, has a default value, this is displayed in the interface when a new item is created (itemtype), but is not saved in the database.
This leads to inconsistent behavior: when GLPI filters search for this value, items supposed to have this default value are not found, as it is not actually saved.
Screenshots (if appropriate):