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

Enrich button doesn't work #9854

Closed
yassine-ouaamou opened this issue Feb 6, 2025 · 1 comment · Fixed by #9856
Closed

Enrich button doesn't work #9854

yassine-ouaamou opened this issue Feb 6, 2025 · 1 comment · Fixed by #9856
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@yassine-ouaamou
Copy link
Member

Description

Can't enrich an IP address

Environment

Testing (6.5)

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to an IP observable
  2. Enrich
  3. { e.g. Error ... }

Expected Output

Actual Output

No action happening

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 Feb 6, 2025
@romain-filigran romain-filigran added the regression Label to identify the bug as a regression of previously working feature label Feb 6, 2025
@nino-filigran nino-filigran added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 6, 2025
@JeremyCloarec JeremyCloarec self-assigned this Feb 6, 2025
@labo-flg
Copy link
Member

labo-flg commented Feb 6, 2025

@JeremyCloarec could you please add an e2e test for that ?

@JeremyCloarec JeremyCloarec linked a pull request Feb 6, 2025 that will close this issue
5 tasks
@SamuelHassine SamuelHassine added this to the Release 6.5.1 milestone Feb 6, 2025
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 6, 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 critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature 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.

6 participants