[Integrates] Priority Tab
Problem to solve
The current priority table view does not provide the necessary flexibility and visibility for users to efficiently manage vulnerabilities.
- The table is not available at the group level, limiting usability.
- The default display shows all locations, including those with accepted treatments (temporary or permanent), which can overwhelm users with irrelevant information.
- Columns in the table lack a standardized structure, making it harder to analyze and act on vulnerabilities.
Intended users
Permissions and Security
Proposal
Introduce the following updates to the priority table view:
-
Group-level access: Move the priority table view to the group level, adding it as the first tab from left to right in the group interface. -
New table columns: Standardize the table structure with the following columns: - Location: Shows where the vulnerability exists.
- Vulnerability: Lists the type of vulnerability.
- Priority Score: Displays the calculated priority score.
- report date
- Treatment: Shows the treatment status (e.g., accepted, under review).
- Assignees: Displays the individuals responsible for handling the vulnerability.
-
Display only locations with a "vulnerable" status and exclude those with an accepted treatment (temporary or permanent). -
Top 50 -
Change last report > Report date -
Mix panel event
Test plan
Steps
-
Make sure that the code contributions checklist has been followed.
What does success look like, and how can we measure that?
Success is defined by:
- Users can efficiently access and use the priority table at the group level.
- The table’s columns provide a clear and actionable overview of vulnerabilities.
- Default filters reduce noise, showing only relevant locations and vulnerabilities.
- Positive feedback from users on the improved usability of the priority table.
Links / references
Edited by Flor Calderon