Technical Spike: Vulnerability Report - Infinite Scrolling vs. Pagination
Problem to solve
As part of the rebuild of the security dashboards Vulnerability Report to use GraphQL, the decision was made for the sake of efficiency that we would use an 'infinite scrolling' approach instead of pagination for displaying long lists of vulnerabilities to our users. This change to infinite scrolling creates issues with the multi-dismissal feature, challenges messaging clearly to the customer how many results are in the list, and in general does not support the customer experience our design team envisioned.
Proposal
Dig into the limitations of GraphQL that caused us to change this behavior in %12.10, find a solution that allows us to present a paginated list of results (20 vulnerabilities per page).
The output of this spike issue will be another issue representing a proposal supporting the following priorities provided by UX/PM:
- Navigating the user back to the same place in the list where they left-off
- Showing total counts
- Persisting sort and filter options when navigating back to the list
Logic Definition
GIVEN a user is on a /security/vulnerability_report
- AND the user has selected one or more vulnerability list items
- WHEN the user clicks to view the next or previous page of list results
- AND the user optionally makes additional selections
- AND the user then clicks to go back to the original page of results
- THEN the user will see the original list items are still selected
- BUT if the user takes an action that reloads the page (applies a filter, navigates away from /security/vulnerability_report [in the same window] and then back, completes a bulk action, or refreshes the page.)
- THEN the selection(s) are cleared
Documentation
Ensure existing documentation is updated to remain accurate
Other references: