Commit 47abb4fd authored by Russell Dickenson's avatar Russell Dickenson

Improve introduction of vulnerability pages

parent 4e12f87c
...@@ -9,10 +9,11 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -9,10 +9,11 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13561) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.0. > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13561) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.0.
Each security vulnerability in the [Security Dashboard](../security_dashboard/index.md#project-security-dashboard) has its own standalone Each security vulnerability in a project's [Security Dashboard](../security_dashboard/index.md#project-security-dashboard) has an individual page which includes:
page.
![Vulnerability page](img/vulnerability_page_v13_1.png) - Details of the vulnerability.
- The status of the vulnerability within the project.
- Available actions for the vulnerability.
On the vulnerability page, you can interact with the vulnerability in On the vulnerability page, you can interact with the vulnerability in
several different ways: several different ways:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment