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

In knowledge tab, table and bar counters doesn't refresh on add/delete element #9838

Open
delemaf opened this issue Feb 5, 2025 · 0 comments · May be fixed by #9867
Open

In knowledge tab, table and bar counters doesn't refresh on add/delete element #9838

delemaf opened this issue Feb 5, 2025 · 0 comments · May be fixed by #9867
Assignees
Labels
bug use for describing something not working as expected filigran team use to identify PR from the Filigran team regression Label to identify the bug as a regression of previously working feature

Comments

@delemaf
Copy link
Member

delemaf commented Feb 5, 2025

Description

Environment

  1. OS (where OpenCTI server runs): N/A
  2. OpenCTI version: All
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go in any Knowledge tab that contains the right bar with entities & observables (ex: Threat Actors Group)
  2. Go to a section (ex: Malwares)
  3. Add an element

Expected Output

The table counter should increment and also the counter in the bar

Actual Output

The table counter doesn't increment, same for the counter in the bar

Additional information

Screenshots (optional)

OpenCTI---Cyber-Threat-Intelligence-Platform.mp4
@delemaf delemaf added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 5, 2025
@delemaf delemaf self-assigned this Feb 5, 2025
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 6, 2025
@delemaf delemaf added filigran team use to identify PR from the Filigran team regression Label to identify the bug as a regression of previously working feature labels Feb 6, 2025
@delemaf delemaf linked a pull request Feb 7, 2025 that will close this issue
5 tasks
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 filigran team use to identify PR from the Filigran team regression Label to identify the bug as a regression of previously working feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants