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

Export panel doesn't appear from the knowledge tab #5735

Closed
yassine-ouaamou opened this issue Jan 29, 2024 · 0 comments
Closed

Export panel doesn't appear from the knowledge tab #5735

yassine-ouaamou opened this issue Jan 29, 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.25

Comments

@yassine-ouaamou
Copy link
Member

Description

Environment

Environment details: Demo (private)

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to a malware
  2. Go to its "Knowledge" and then select Indicators on the right
  3. Select some or all indicators and try to export them

Expected Output

The export panel should appear

Actual Output

No export panel appears

Additional information

Screenshots (optional)
@yassine-ouaamou yassine-ouaamou added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 29, 2024
@yassine-ouaamou yassine-ouaamou changed the title Export panel doesn't appear Export panel doesn't appear from the knowledge tab Jan 29, 2024
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 29, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.25 milestone Jan 29, 2024
SamuelHassine added a commit that referenced this issue Jan 29, 2024
@SamuelHassine
[frontend] Fix export panel in indicators entities view (#5735)
3e4c3c4
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 29, 2024
@SamuelHassine SamuelHassine self-assigned this Jan 29, 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.25
Development

No branches or pull requests
2 participants
@SamuelHassine @yassine-ouaamou