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

[Dashboard] "Number of results" not taken into account #5578

Closed
Lhorus6 opened this issue Jan 17, 2024 · 0 comments · Fixed by #5588
Closed

[Dashboard] "Number of results" not taken into account #5578

Lhorus6 opened this issue Jan 17, 2024 · 0 comments · Fixed by #5588
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Lhorus6
Copy link

Lhorus6 commented Jan 17, 2024

Description

When I create a "List" > "Activity & History" widget, the "Number of results" parameter in the 4th configuration step is not taken into account. (not critical at all)

Environment

OCTI 5.12.19

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a widget List > Activity & History
  2. In "3. Filters" : No filter
  3. In "4. Parameters" : Number of results = 10
    -> You get more than 10 entities in the list

See dashboard "issue/5578" on the filigran platform

Screenshots

On the left, the buggy config described above, on the right the same config in "Entity" perspective (which is not buggy):

Screenshot 2024-01-17 230301

@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 Jan 17, 2024
@nino-filigran nino-filigran added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team needs more info Intel needed about the use case labels Jan 18, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.21 milestone Jan 18, 2024
@CelineSebe CelineSebe self-assigned this Jan 18, 2024
@CelineSebe CelineSebe linked a pull request Jan 18, 2024 that will close this issue
5 tasks
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 18, 2024
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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants