Fixed invalid custom fields being used for filtering#17544
Merged
snipe merged 2 commits intogrokability:developfrom Aug 15, 2025
Merged
Fixed invalid custom fields being used for filtering#17544snipe merged 2 commits intogrokability:developfrom
snipe merged 2 commits intogrokability:developfrom
Conversation
This was referenced Aug 18, 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
2 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.
This PR fixes an issue where invalid custom fields were being accepted and used for filtering. Now the
$filteris run througharray_filterchecked against$allowed_columnsand valid custom field keys.[RB-20068]
[RB-20069]