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

Full refactor of pre-validation screen into an analyst workbench #2408

Closed
SamuelHassine opened this issue Oct 2, 2022 · 2 comments · Fixed by #2466
Closed

Full refactor of pre-validation screen into an analyst workbench #2408

SamuelHassine opened this issue Oct 2, 2022 · 2 comments · Fixed by #2466
Assignees
@SamuelHassine
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 5.4.0

Comments

@SamuelHassine
Copy link
Member

Use case

Refactor the pre-validation screen into an analyst temporary workbench:

  • Lines/Columns layout
  • Save current state
  • Add new element
  • Be able to add columns for new relationship (victimology, attribution)
  • Remember choices for adaptive behavior over time
@SamuelHassine SamuelHassine added this to the Release 5.4.0 milestone Oct 2, 2022
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Oct 2, 2022
@SamuelHassine SamuelHassine self-assigned this Oct 2, 2022
This was referenced Oct 2, 2022
Closed
Open
Open
@SamuelHassine
Copy link
Member Author

Related to #1799.

@SamuelHassine SamuelHassine mentioned this issue Oct 18, 2022
Merged
5 tasks
@SamuelHassine SamuelHassine linked a pull request Oct 18, 2022 that will close this issue
[api/frontend] Implement a first version of the analyst workbench (#2408) #2466
Merged
5 tasks
SamuelHassine added a commit that referenced this issue Oct 19, 2022
@SamuelHassine
[api/frontend] Implement a first version of the analyst workbench (#2408
fca3023 
, #2163, #1799)
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 19, 2022
@SamuelHassine SamuelHassine reopened this Oct 19, 2022
SamuelHassine added a commit that referenced this issue Oct 20, 2022
@SamuelHassine
[frontend] Bulk apply marking definitions in the analyst workbench (#…
fe5253b 
…2408)
SamuelHassine added a commit that referenced this issue Oct 21, 2022
@SamuelHassine
[frontend] Fix some bugs in the analyst workbench (#2408)
0ff4a57
@kudrew
Copy link

kudrew commented Nov 1, 2022 •
edited

@SamuelHassine from testing this in Demo and comparing it to 5.3.17, importing the same pdf will give different results.

Also on Demo, adding entities manually in the workbench section of the validation screen and validating will create them on the platform, but doesn't add them to the report.

@kudrew kudrew mentioned this issue Nov 22, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 5.4.0
Development

Successfully merging a pull request may close this issue.

[api/frontend] Implement a first version of the analyst workbench (#2408) OpenCTI-Platform/opencti
2 participants
@SamuelHassine @kudrew