Skip to content

Added 'user reports' in the history page#2895

Merged
drosetti merged 13 commits intofrontend_analyzablesfrom
user_reports_history
Jun 17, 2025
Merged

Added 'user reports' in the history page#2895
drosetti merged 13 commits intofrontend_analyzablesfrom
user_reports_history

Conversation

@carellamartina
Copy link
Contributor

@carellamartina carellamartina commented Jun 16, 2025

Description

Added 'user reports' in the history page

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

  • I have read and understood the rules about how to Contribute to this project
  • The pull request is for the branch develop
  • A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
    • I strictly followed the documentation "How to create a Plugin"
    • Usage file was updated. A link to the PR to the docs repo has been added as a comment here.
    • Advanced-Usage was updated (in case the plugin provides additional optional configuration). A link to the PR to the docs repo has been added as a comment here.
    • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration. ("How to share a plugin with the community")
    • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip and you added the default tests for that mimetype in test_classes.py.
    • If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook by following this guide.
    • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
    • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
    • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information. This is required for Health Checks (HEAD HTTP requests).
    • If the plugin requires mocked testing, _monkeypatch() was used in its class to apply the necessary decorators.
    • I have added that raw JSON sample to the MockUpResponse of the _monkeypatch() method. This serves us to provide a valid sample for testing.
    • I have created the corresponding DataModel for the new analyzer following the documentation
  • I have inserted the copyright banner at the start of the file: # This file is a part of IntelOwl https://github.com/intelowlproject/IntelOwl # See the file 'LICENSE' for copying permission.
  • Please avoid adding new libraries as requirements whenever it is possible. Use new libraries only if strictly needed to solve the issue you are working for. In case of doubt, ask a maintainer permission to use a specific library.
  • If external libraries/packages with restrictive licenses were added, they were added in the Legal Notice section.
  • Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors.
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.
  • After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review by using GitHub's reviewing system detailed here.

@carellamartina
Copy link
Contributor Author

carellamartina commented Jun 16, 2025

Schermata del 2025-06-11 14-53-19

@carellamartina carellamartina requested a review from drosetti June 16, 2025 10:07
drosetti
drosetti requested changes Jun 16, 2025
View reviewed changes
Copy link
Contributor

@drosetti drosetti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the user reports table a see a report as decayed, but in the analyzable page I don't see the decay value. Try this to reproduce the bug:
Run an analysis for 8.8.8.8
Then paste this code in the shell:

from certego_saas.apps.user.models import User
from api_app.analyzables_manager.models import Analyzable
from api_app.data_model_manager.models import DomainDataModel
from api_app.user_events_manager.models import UserAnalyzableEvent

u = User.objects.get(username="admin")
a = Analyzable.objects.get(name="8.8.8.8")
dm = DomainDataModel(evaluation="malicious", reliability=9, related_threats=["this is a test"])
dm.save()
ue = UserAnalyzableEvent(user=u, analyzable=a, data_model=dm)
ue.save()

You should be able to replicate.
Screenshot from 2025-06-16 18-11-07
Screenshot from 2025-06-16 18-11-15

@carellamartina carellamartina requested a review from drosetti June 17, 2025 12:53
@drosetti drosetti merged commit 2f0f7a7 into frontend_analyzables Jun 17, 2025
4 checks passed
@drosetti drosetti deleted the user_reports_history branch June 17, 2025 13:40
drosetti added a commit that referenced this pull request Jul 31, 2025
@carellamartina @drosetti
Frontend - analyzables page + user events modal (#2931)
8de0446 
* Frontend - Analyzables page (#2865)

* adjusted menu

* analyzables page draft + refactor

* adjusted table columns and serializer

* frontend tests

* tests

* prettier

* fix

* changes

* fix

* Analyzable overview page (#2883)

* analyzable overview page draft

* refactor

* visualizers draft

* Analyzable overview page

* prettier

* removed cache

* changes

* adjusted tests

* fixed decay date visualizer

* use enum

---------

Co-authored-by: drosetti <[email protected]>

* added data model tab (#2900)

* Added 'user reports' in the history page (#2895)

* added user-reports page

* fix

* changes

* tests

* changes

* prettier

* fixed decayed badge

* fix

* User events modal form (#2928)

* form draft

* adjusted backend

* adjusted analyzable history

* fix

* fixed evaluation modal

* renamed user reports to user events

* renamed analyzable to artifact in the gui

* adjusted frontend tests

* fix

* frontend tests

* fix frontend tests

* prettier

* fix

* fix

* fix

* refactor history tables

* fix

---------

Co-authored-by: drosetti <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@drosetti drosetti drosetti approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@carellamartina @drosetti