Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • See what's new at GitLab
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,392
    • Issues 34,392
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,155
    • Merge Requests 1,155
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Merge Requests
  • !40993

Merged
Opened Sep 01, 2020 by James Johnson@d0c-s4vageDeveloper6 of 13 tasks completed6/13 tasks

Adds documentation for CVE ID Request button

  • Overview 37
  • Commits 10
  • Pipelines 10
  • Changes 10

What does this MR do?

This MR adds documentation for the CVE ID Request button in the issue sidebar. This MR is the documentation portion of Draft: Adds Request CVE ID button to issue sidebar, which was broken into separate merge requests.

For an overview of what purpose the button serves, please see the video below, or read the high-level bullet points below the video:

image Slides

  • CVE identifiers track specific vulnerabilities in specific version ranges of a project
  • GitLab participates in MITRE's CNA program and is able to issue CVE identifiers to projects that are:
    • public
    • hosted on GitLab.com
  • Prior to this feature, users needed to manually create an issue to start the CVE request process
  • The CVE ID Request button allows project maintainers to directly create the CVE ID Request issue from an existing, confidential issue's sidebar

The CVE ID Request button is only available

  • when the project is public
  • when the project is hosted on GitLab.com
  • when the current user is a maintainer
  • when the current issue is a confidential issue

Screenshots

Does this MR meet the acceptance criteria?

Conformity

  • Changelog entry Not needed - docs only change
  • Documentation (if required)
  • Code review guidelines
  • Merge request performance guidelines
  • Style guides
  • Database guides
  • Separation of EE specific content

Availability and Testing

  • Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
  • Tested in all supported browsers
  • Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited Sep 02, 2020 by James Johnson
Assignee
Assign to
Reviewer
Request review from
13.4
Milestone
13.4 (Past due)
Assign milestone
Time tracking
Reference: gitlab-org/gitlab!40993
Source branch: add_request_cve_issue_docs

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.