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.

Sign up for GitHub

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

Jump to bottom

[Dashboard] Counter view not correct #5706

Closed
Lhorus6 opened this issue Jan 26, 2024 · 0 comments
Closed

[Dashboard] Counter view not correct #5706

Lhorus6 opened this issue Jan 26, 2024 · 0 comments
Assignees
@SamuelHassine
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)
Milestone
Release 5.12.22

Comments

@Lhorus6
Copy link

Lhorus6 commented Jan 26, 2024 •
edited

Description

The number displayed in the counters widget ("number" view) is not correct. You can see this by displaying a list widget and a counter widget with the same filters, and the results obtained are not consistent.

Environment

OCTI 5.12.21

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create 2 Reports and assigned them to you
  2. Create a widget "numbers > entities" with the filter : "Entity type = Report AND assignee = [you]"
  3. Same config but with a widget "list"
    -> The results obtained are not consistent.

You can find my dashboard on the filigran prod instance. It's called "issue/5706 DO NOT MODIFY"

Screenshots

Dashboard

Dashboard

List view config

List_view_config

Number view config

Number_view_config
@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 26, 2024
@SamuelHassine SamuelHassine self-assigned this Jan 26, 2024
SamuelHassine added a commit that referenced this issue Jan 26, 2024
@SamuelHassine
[frontend] Fix number of objects widgets (#5706)
a53ab8c
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 26, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.22 milestone Jan 26, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

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
Milestone
Release 5.12.22
Development

No branches or pull requests
2 participants
@SamuelHassine @Lhorus6