## Summary * Use GraphQL for fetching data and interactions on the pipeline security report * Another goal is to share as many components as possible with the Vulnerability Report (Details Section, etc.) * Some work has already been done and is currently deployed behind a feature flag: `pipeline_security_dashboard_graphql` * These areas are in scope for this epic: | Area | Sub-epic | | ------ | ------ | | Create reusable findings modal | https://gitlab.com/groups/gitlab-org/-/epics/8910 | | Pipeline/Security Findings Listing | https://gitlab.com/groups/gitlab-org/-/epics/8478 | | Finding Modal content | https://gitlab.com/groups/gitlab-org/-/epics/8459 | | Finding Modal actions | https://gitlab.com/groups/gitlab-org/-/epics/8479 | Previous epic: &4969 ## Maintenance tasks * https://gitlab.com/gitlab-org/gitlab/-/issues/300757 * https://gitlab.com/gitlab-org/gitlab/-/issues/328818 ## Questions for ~UX and ~"Product Management" * We are currently sharing the listing-component with the Vulnerability Report, which does not contain the "Hide Dimiss" button. Is this a feature we want to keep, since the user can now use the filters to achieve the same result? If we want to keep it - would it also make sense to have it on the Vulnerability report? * The current version of the pipeline has a table-column that contains a few action buttons for dismissal, [undo-dismissal](https://gitlab.com/groups/gitlab-org/-/uploads/162cdbc2a3cb2f56fb15d238440d3be6/Screen_Shot_2022-05-12_at_4.22.49_pm.png) and [issue creation](https://gitlab.com/groups/gitlab-org/-/uploads/1d6ad337c9bc635d76774f31884afbd4/Screen_Shot_2022-05-11_at_11.47.51_am.png). Do we want to keep the column or move those actions somewhere else? * We also currently show a finding's related issues: https://gitlab.com/groups/gitlab-org/-/uploads/2709d0704ac81bcd403be6bff5a155d1/Screen_Shot_2022-05-10_at_9.34.28_pm.png On the vulnerability report we have this information in the "activity" column. I guess this will be the same for the new version of the pipeline report?