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

Donut widget type displays multiple of the same entries #9929

Open
fruitcakej opened this issue Feb 11, 2025 · 1 comment
Open

Donut widget type displays multiple of the same entries #9929

fruitcakej opened this issue Feb 11, 2025 · 1 comment
Assignees
Labels
bug use for describing something not working as expected
Milestone

Comments

@fruitcakej
Copy link

Description

When creating a dashboard widget of type “Donut”, perspective “Entities” with filters Label and Parameters attribute set to “Status”, multiple entries are displayed.

The intention of this dashboard widget is to display the distribution of statuses for RFIs, Incident Responses and Tasks with the label.

Environment

6.5.1 SaaS

Reproducible Steps

Steps to create the smallest reproducible scenario:

From a dashboard, create a widget
Select the “Donut” Visualisation
Select the “Entities” Perspective
Filter for the labels
Under Parameters > Attribute, select “Status”

Expected Output

Actual Output

Multiple entries for fields are displayed

Screenshots (optional)

(recreated in testing with following labels)

Image

Image

@fruitcakej fruitcakej added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 11, 2025
@nino-filigran
Copy link

@fruitcakej the reason is because you may have different entity types. Each of them has a status NEW, but this "NEW" status has a different id for each entity type, leading to this situation (it is interpreted as 2 different statuses in the end).
Therefore, this is "normal", but I agree, far from being optimal.

Given that we have fixed this behavior in the filters of the platform (for instance, if you try the same query on data entity, only a single status NEW will be available), we should do the same in the dashboards.

@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 12, 2025
@marieflorescontact marieflorescontact self-assigned this Feb 13, 2025
@nino-filigran nino-filigran added this to the Bugs backlog milestone Feb 14, 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

3 participants