<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=362397) </details> <!--IssueSummary end--> ## Intent When utilizing GitLab's Slack notification service you may configure **Vulnerability** triggers. With this feature, it would be nice to have further triggers available for further audit visibility around vulnerability dismissals as well. ## Proposal There should possible be an option for creating a **Vulnerability Dismissal** trigger. This payload should include the “dismissal reason”, the “dismissed at”, and “dismissed by” within GraphQL. ## References Dismissal of vulnerabilities is stored within the https://docs.gitlab.com/ee/api/project_vulnerabilities.html, and will report within two portions of the object response: "dismissed_at": null, "dismissed_by_id": null, Note that the API is in the process of deprecation, but the same responses can also be generating using the GraphQL API https://docs.gitlab.com/ee/api/graphql/reference/#fields-757