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

Configurable Severity #155

Closed
zimventures opened this issue Aug 15, 2023 · 0 comments · Fixed by #161
Closed

Configurable Severity #155

zimventures opened this issue Aug 15, 2023 · 0 comments · Fixed by #161
Assignees

Comments

@zimventures
Copy link
Contributor

While we're doing the refactor, it would be useful to update the severity field to be its own model (instead of just an IntegerField).
The new Severity model would contain:

name (str)
value (int)
color (hexidecimal color value)

Out of the box, the system will define some basic severity levels (low, medium, high, critical, etc...). These should be installed as fixtures as part of the application initialization.

Views

Severity Management

A single view will exist that allows for severities to be listed, created, and archived. For creating a new severity, a button will open a modal which contains the 3 required fields (name, value, color). Upon submitting the values in the modal, the user should be redirected back to the severity management dashboard. Clicking on the archive button for a severity should prompt the user with a confirmation dialog. Upon accepting the archive prompt, the modal is closed and the DIV with the severity is removed as a result of the HTMX call.

Finding Severity Formatting

The existing finding tab within the scan result page has a column for severity. This column should be updated to show the priority name, value, and use the specified color.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants