-
Notifications
You must be signed in to change notification settings - Fork 2
Cases #39
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
Open
anidev95
wants to merge
63
commits into
main
Choose a base branch
from
cases
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…f a user selects an entity in the details page the user will be sent to the alerts page which will show all the alerts for the selected entity.
…for displaying all the cases for filtered user and another subcomponent that will show detailed information for the selected case.
…viders more easily than individually.
…viders more easily than individually.
…viders more easily than individually.
… back to the user once the case has been created. Also added and updated database schema to include cases.
… back to the user once the case has been created. Also added and updated database schema to include cases.
…e to the user interface. Next item being worked on is having cases be filtered based on priority.
…ory per case for the cases feature.
…s and continuing work on cases feature.
…ase or comment are created it will immediately appear in the UI.
…lp perform data sanitization on the flask backend.
… on the flask backend.
…in cases details page to prevent overflow on page. Also added vertical scrollbar to comments in the cases details page.
…mption in the flask backend.
…case details page based on the entity being investigated in the case.
… agent/llm to post an initial comment summarizing what the case is for to help the user have an idea how to investigate the entity.
…ed color coding so that the user will be able to distinguish between a llm/agent comment and a user comment.
…f the application.
…d cases to be ingested by agents and be analyzed.
… The case will now be created without needing to wait for the comment to be generated. Comment is inserted in the backend and it will show up in case once it's generated.
… to clear filters. In addition to this, I've removed the select case button and chat on the right side of the cases page as there isn't a need for it.
…mports in skynet-react.
…nter a case name after accidentally not entering it in. There was a minor bug where you have to click cancel for it to work. This resolves that issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.