Skip to content
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

Incomplete search for Observable User Account entities. #10094

Open
Lhorus6 opened this issue Feb 26, 2025 · 0 comments
Open

Incomplete search for Observable User Account entities. #10094

Lhorus6 opened this issue Feb 26, 2025 · 0 comments
Labels
bug use for describing something not working as expected
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Feb 26, 2025

Description

Depending on the fields filled in an Observable User Account, it may not be possible to find it using the search. The problem is that the “User” field of an Observable User Account is not taken into account in the search. The same applies to the “Account login” field (and probably others).

Environment

OCTI 6.5.3

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create an Observable User Account with the “User” field set to "myuseraccounttest"

  2. Search for “myuseraccounttest” in the search bar
    -> you won't find anything.

  3. Now delete this User Account and create a new one with field “User” = ewhatyouwante and “Display name” = "myuseraccounttest"

  4. Repeat the search for “myuseraccounttest”, this time you'll find the User Account

Expected Output

I expect to find my User Account if I search for a value contained in the text fields of my User Account, or at least in the mandatory fields.

Actual Output

The “Display name” field (which is not mandatory) is taken into account by search methods, but “User” and “Account login”, which are mandatory fields, are not (and perhaps others).

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 26, 2025
@alice-debra alice-debra removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 27, 2025
@alice-debra alice-debra added this to the Bugs backlog milestone Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants