Done but may be waiting for review to close

We will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

priority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority

Issues for findings from a May 2018 penetration test from an external contractor

Items related to security product offerings such as SAST and DAST

Docs Priority 1 - Urgent: The current release.

Docs Priority 2 - High: The next release.

Docs Priority 3 - Medium: Within the next 3 releases (approx one quarter).

Docs Priority 4 - Low: Anything outside the next 3 releases (approx beyond one quarter).

Issues related to Infrastructure Architecture

For issues that relate to or involve a free user.

A production incident that has any customer impact

The content of the issue or comments contains to references to private user information, such as private repository paths and its contents should remain confidential indefinitely. This is usually primarily used for ~security or production issues.

Issues for important features that are on our roadmap: https://about.gitlab.com/direction/