Security Data in Merge Request Iteration 2: Include Full Data Set
## Executive Summary The MR widget is not delightful to developers because the complete set of scan data is dumped on them. Results need to be carefully curated for developers in the appropriate place, the appropriate results with the appropriate context should be presented, and the appropriate workflows should be supported. This epic improves the place (a new tab), and the type of results (blockers). ## Business Case see parent epic. Explicit Customer Asks: SEI ## Scope ### In scope 1. Instead of including a subset of vulnerabilities, include all vulnerabilities from that pipeline run. 1. Right now there is a limit of 10-25 vulnerabilities in the widget, and can be randomly arranged leading to confusion and pain ## Implementation ```glql display: table sort: milestone asc fields: title, labels("backend","frontend","documentation") as "Type", status, milestone, assignee query: epic = &20760 and type = Issue ```
epic