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

Jump to bottom

Implement the investigation graph with workspaces #21

Closed
manonviallet opened this issue Apr 17, 2019 · 0 comments
Closed

Implement the investigation graph with workspaces #21

manonviallet opened this issue Apr 17, 2019 · 0 comments
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 4.3.2

Comments

@manonviallet
Copy link
Contributor

manonviallet commented Apr 17, 2019 •
edited by SamuelHassine

Problem to Solve

The user must be able to explore the data of the platform within a graph by searching for neighbors and so visualize the database.

Current Workaround

None.

Proposed Solution

Implement the concept of "workspace", implement an exploration graph view.

Additional Information

None.
@SamuelHassine SamuelHassine added this to the 1.0-beta milestone Apr 20, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 20, 2019
@SamuelHassine SamuelHassine self-assigned this Apr 20, 2019
@SamuelHassine SamuelHassine modified the milestones: v1.0.0-beta, v1.0.0 Jun 17, 2019
@SamuelHassine SamuelHassine added this to the Release 3.3.0 milestone Apr 23, 2020
SamuelHassine pushed a commit that referenced this issue Mar 25, 2021
[api/frontend] First work on investigations, fix search (#1199, #21)
7670420
richard-julien pushed a commit that referenced this issue Mar 26, 2021
@richard-julien
[api/frontend] First work on investigations, fix search (#1199, #21)
3392e2e
SamuelHassine pushed a commit that referenced this issue Mar 26, 2021
[api/frontend] Investigation graphs enhancements (#21)
dd9890e
SamuelHassine pushed a commit that referenced this issue Mar 26, 2021
[api/frontend] Finish first work around investigation (#21)
e4b5e26
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 26, 2021
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 4.3.2
Development

No branches or pull requests
2 participants
@SamuelHassine @manonviallet