As part of https://gitlab.com/groups/gitlab-org/-/epics/8054+, this epic is focused on migrating the pipeline security listing table to GraphQL and retaining feature parity. Work is done behind the `:pipeline_security_dashboard_graphql` feature flag. It is enabled in the verification project [security-reports-pipeline-security-listing-migration-and-enhancements](https://gitlab.com/gitlab-org/govern/threat-insights-demos/verification-projects/security-reports-pipeline-security-listing-migration-and-enhancements/-/pipelines/1100011493/security) ## Scope of work ### MVC * Bulk state (status) change for dismissal and needs triage * Related issue (activity column) * Status filtering (without dismissal reason) * Show dismissal reason * https://gitlab.com/gitlab-org/gitlab/-/issues/436975+ ### Post-MVC * Bulk state change for all states (add confirmed and resolved) * Dismissal reason filtering * Sorting * Activity column * Activity filter * Custom tool filtering <table> <tr> <th>Description</th> <th>Current</th> <th>Behind feature flag</th> <th>Issues</th> <th>Comments</th> </tr> <tr> <td>Overview</td> <td>  </td> <td>  </td> <td> </td> <td> </td> </tr> <tr> <td>Show dismissal reason</td> <td>N/A</td> <td>  </td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/432910+s, ~backend 2. https://gitlab.com/gitlab-org/gitlab/-/issues/433336+s, ~frontend </td> <td>The UI supports showing the dismissal reason badge, but the frontend needs to request the dismissal reason from the backend</td> </tr> <tr> <td>Related issue</td> <td>  </td> <td>Not yet implemented</td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/362575+, ~frontend 2. https://gitlab.com/gitlab-org/gitlab/-/issues/433477+, ~frontend </td> <td>The vulnerability report has a column for this called "Activity", follow the same pattern here.</td> </tr> <tr> <td>Bulk state changes</td> <td>  <small>note: only dismissal and dismissal reasons aren't the canonical ones</small> </td> <td>  </td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/331408+s 2. https://gitlab.com/gitlab-org/gitlab/-/issues/431818+s </td> <td>The UI is working but the mutations for findings are not linked and we currently only have mutations for findings for dismissing and reverting to detected, not for confirmed or resolved.</td> </tr> <tr> <td>"Dismissed as ..." filtering</td> <td> N/A <small>note: only a toggle to hide/show dismissed findings</small> </td> <td>  </td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/433033+s, ~backend 2. https://gitlab.com/gitlab-org/gitlab/-/issues/433337+s, ~frontend </td> <td>The UI is working, but the findings query does not support dismissal reasons filtering. There is some backend work required.</td> </tr> <tr> <td>Technical Debt</td> <td> </td> <td> </td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/355840+s 2. https://gitlab.com/gitlab-org/gitlab/-/issues/362579+s 3. https://gitlab.com/gitlab-org/gitlab/-/issues/300757+s 4. https://gitlab.com/gitlab-org/gitlab/-/issues/431796+s 5. https://gitlab.com/gitlab-org/gitlab/-/issues/431800+s </td> <td>Issues tracking non-feature or functional changes.</td> </tr> <tr> <td>Filtered result empty state</td> <td>  </td> <td>  <small>note: the vulnerability report renders "Sorry, your filters produced no resuls"</small> </td> <td> https://gitlab.com/gitlab-org/gitlab/-/issues/362576+ </td> <td>The current behavior is the same as the one behind the feature flag, however on the vulnerability report we see a more specific message</td> </tr> <tr> <td>Sorting</td> <td>N/A</td> <td>  </td> <td> 1. https://gitlab.com/gitlab-org/gitlab/-/issues/360480+s, ~backend 2. https://gitlab.com/gitlab-org/gitlab/-/issues/361152+s, ~frontend </td> <td> Sortable columns: 1. Severity 2. Status 3. Description 4. Tool This is a ~"feature::enhancement". The current pipeline table does not show any sorting. </td> </tr> <tr> <td>Activity column (other than related issue)</td> <td>N/A</td> <td>  </td> <td> </td> <td> UI can be reused. This is ~"feature::enhancement". There is some backend work to add the required filters to the GraphQL query. </td> </tr> <tr> <td>Activity filtering</td> <td>N/A</td> <td>  </td> <td> </td> <td> This is ~"feature::enhancement" UI can be reused. There is some backend work to add the required filters to the GraphQL query. </td> </tr> <tr> <td>Custom-tool filtering</td> <td>N/A</td> <td>  </td> <td> </td> <td> This is ~"feature::enhancement" UI can be reused. There is some backend work to add the required filters to the GraphQL query. </td> </tr> <tr> <td>Create related issue (action button)</td> <td>  </td> <td>Will not implement</td> <td> </td> <td></td> </tr> <tr> <td>Create related Jira issue (action button)</td> <td>  </td> <td>Will not implement</td> <td> </td> <td> </td> </tr> <tr> <td>Undo dismissal (action button)</td> <td>  </td> <td>Will not implement</td> <td> </td> <td> </td> </tr> </table>