Skip to content

docs: describe the In List and Not in List operators on text column filters - #16359

Closed
stevewallone wants to merge 1 commit into
DefectDojo:devfrom
stevewallone:docs/text-filter-in-list
Closed

stevewallone wants to merge 1 commit into
DefectDojo:devfrom
stevewallone:docs/text-filter-in-list

Conversation

@stevewallone

Copy link
Copy Markdown
Contributor

Description

A "How text filters are evaluated" section on the Pro Filter Index page, next to the existing date and number sections. It names the eight single-value text operators and the two new list ones, In List and Not in List: type or paste values separated by commas, new lines or tabs, each becomes a chip, In List keeps the rows whose value equals any chip and Not in List removes them. It also states the rules a reader needs to predict a result: every text operator is case-insensitive, In List compares whole values rather than fragments, chips are trimmed and empty ones ignored, an empty list applies no filter, and a value containing a comma cannot be listed because the list travels comma-joined in the table URL and saved preferences.

Pairs with the Pro change that adds the two modes to every text column filter in the Vue lists. Pro PR number: 4068.

Docs only, English page only (translations are regenerated separately).

🤖 Generated with Claude Code

…ilters

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@stevewallone stevewallone left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review

Recommendation: approve. Head reviewed: cf57683e92, base dev, one new section on docs/content/navigation/PRO__filter_index.md, description text-only.

Checked against the paired Pro change running on a stack:

  • Paste splitting on commas, new lines and tabs, trimming, dropped blanks and duplicates, and an empty list applying no filter all behave as written (verified with a pasted CRLF/tab/blank/duplicate list and with a 150-value list).
  • Case-insensitive whole-value matching is what the backend does (iexact per value), and Not in List keeps rows whose field is empty, which the page does not need to say.
  • The comma limitation is accurate: the list travels comma-joined, so a value holding a comma cannot be listed.

One thing the page cannot yet promise: on the Pro side the custom-field text columns offer the two operators but do not apply them (raised on the Pro PR as a blocker). Once that is fixed the text here holds for every text column it names; if the Pro fix narrows those columns instead, this section should say custom-field columns take the single-value operators only.

Nothing to change in the wording.

@stevewallone

Copy link
Copy Markdown
Contributor Author

The paired Pro change (PR number 4068) merged to Pro dev on 2026-10-15 for release 3.4.200. This docs PR is ready to merge alongside it; it still needs a maintainer to set the 3.4.200 milestone.

@blakeaowens

Copy link
Copy Markdown
Contributor

Superseded by #16406, which documents the reworked list filters (In List / Not in List on text filters, Include / Exclude, In List of names on the Asset and Organization filters, and the size limit) in one change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants