@@ -8121,11 +8121,11 @@ The dismissal reason of the Vulnerability.
| Value | Description |
| ----- | ----------- |
| `ACCEPTABLE_RISK` | The likelihood of the Vulnerability occurring and its impact are deemed acceptable |
| `FALSE_POSITIVE` | The Vulnerability was incorrectly identified as being present |
| `MITIGATING_CONTROL` | There is a mitigating control that eliminates the Vulnerability or makes its risk acceptable |
| `NOT_APPLICABLE` | Other reasons for dismissal |
| `USED_IN_TESTS` | The Vulnerability is used in tests and does not pose an actual risk |
| `ACCEPTABLE_RISK` | The vulnerability is known, and has not been remediated or mitigated, but is considered to be an acceptable business risk. |
| `FALSE_POSITIVE` | An error in reporting in which a test result incorrectly indicates the presence of a vulnerability in a system when the vulnerability is not present. |
| `MITIGATING_CONTROL` | A management, operational, or technical control (that is, safeguard or countermeasure) employed by an organization that provides equivalent or comparable protection for an information system. |
| `NOT_APPLICABLE` | The vulnerability is known, and has not been remediated or mitigated, but is considered to be in a part of the application that will not be updated. |
| `USED_IN_TESTS` | The finding is not a vulnerability because it is part of a test or is test data. |
@@ -50,16 +50,16 @@ These notification settings apply only to you. They do not affect the notificati
## Global notification settings
Your **Global notification settings** are the default settings unless you select different values for a project or a group.
Your **Global notification settings** are the default settings unless you select
different values for a project or a group.
- Notification email
- This is the email address your notifications are sent to.
- Global notification level
- This is the default [notification level](#notification-levels) which applies to all your notifications.
- Receive product marketing emails
- Check this checkbox if you want to receive periodic emails related to GitLab features.
- Receive notifications about your own activity.
- Check this checkbox if you want to receive notification about your own activity. Default: Not checked.
-**Notification email**: The email address your notifications are sent to.
-**Global notification level**: The default [notification level](#notification-levels)
which applies to all your notifications.
-**Receive product marketing emails**: Select this check box to receive periodic
emails about GitLab features.
-**Receive notifications about your own activity**: Select this check box to receive
notifications about your own activity. Not selected by default.
### Notification scope
...
...
@@ -67,16 +67,16 @@ You can tune the scope of your notifications by selecting different notification
Notification scope is applied in order of precedence (highest to lowest):
-Project
- For each project, you can select a notification level. Your project setting overrides the group setting.
-Group
- For each group, you can select a notification level. Your group setting overrides your default setting.
-Global (default)
- Your global, or _default_, notification level applies if you have not selected a notification level for the project or group in which the activity occurred.
-**Project**: For each project, you can select a notification level. Your project
setting overrides the group setting.
-**Group**: For each group, you can select a notification level. Your group setting
overrides your default setting.
-**Global (default)**: Your global, or _default_, notification level applies if you
have not selected a notification level for the project or group in which the activity occurred.
#### Project notifications
You can select a notification level for each project. This can be useful if you need to closely monitor activity in select projects.
You can select a notification level for each project to help you closely monitor activity in select projects.
@@ -242,19 +242,38 @@ with a link to the commit that resolved the issue.
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3622) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
You can browse and search issues from a selected Jira project directly in GitLab. This requires [configuration](#configure-gitlab) in GitLab by an administrator.
You can browse, search, and view issues from a selected Jira project directly in GitLab,
if your GitLab administrator [has configured it](#configure-gitlab):
1. In the left navigation bar, go to **Jira > Issues list**.
1. The issue list sorts by **Created date** by default, with the newest issues listed at the top:
From the **Jira Issues** menu, click **Issues List**. The issue list defaults to sort by **Created date**, with the newest issues listed at the top. You can change this to **Last updated**.
Issues are grouped into tabs based on their [Jira status](https://confluence.atlassian.com/adminjiraserver070/defining-status-field-values-749382903.html).
1. To display the most recently updated issues first, click **Last updated**.
1. In GitLab versions 13.10 and later, you can view [individual Jira issues](#view-a-jira-issue).
Issues are grouped into tabs based on their [Jira status](https://confluence.atlassian.com/adminjiraserver070/defining-status-field-values-749382903.html):
- The **Open** tab displays all issues with a Jira status in any category other than Done.
- The **Closed** tab displays all issues with a Jira status categorized as Done.
- The **All** tab displays all issues of any status.
Click an issue title to open its original Jira issue page for full details.
#### View a Jira issue
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/299832) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.10.
> - It's [deployed behind a feature flag](../../feature_flags.md), disabled by default.
> - It's enabled on GitLab.com.
> - It's recommended for production use.
> - For GitLab self-managed instances, GitLab administrators can opt to [enable it](#enable-or-disable-jira-issue-detail-view). **(PREMIUM)**
WARNING:
This feature might not be available to you. Check the **version history** note above for details.
When viewing the [Jira issues list](#view-jira-issues), select an issue from the
description'The dismissal reason of the Vulnerability'
definedo
acceptable_riskvalue: 0,description: 'The likelihood of the Vulnerability occurring and its impact are deemed acceptable'
false_positivevalue: 1,description: 'The Vulnerability was incorrectly identified as being present'
mitigating_controlvalue: 2,description: 'There is a mitigating control that eliminates the Vulnerability or makes its risk acceptable'
used_in_testsvalue: 3,description: 'The Vulnerability is used in tests and does not pose an actual risk'
not_applicablevalue: 4,description: 'Other reasons for dismissal'
acceptable_riskvalue: 0,description: _('The vulnerability is known, and has not been remediated or mitigated, but is considered to be an acceptable business risk.')
false_positivevalue: 1,description: _('An error in reporting in which a test result incorrectly indicates the presence of a vulnerability in a system when the vulnerability is not present.')
mitigating_controlvalue: 2,description: _('A management, operational, or technical control (that is, safeguard or countermeasure) employed by an organization that provides equivalent or comparable protection for an information system.')
used_in_testsvalue: 3,description: _('The finding is not a vulnerability because it is part of a test or is test data.')
not_applicablevalue: 4,description: _('The vulnerability is known, and has not been remediated or mitigated, but is considered to be in a part of the application that will not be updated.')
msgid "A limit of %{ci_project_subscriptions_limit} subscriptions to or from a project applies."
msgstr ""
msgid "A management, operational, or technical control (that is, safeguard or countermeasure) employed by an organization that provides equivalent or comparable protection for an information system."
msgstr ""
msgid "A member of the abuse team will review your report as soon as possible."
msgstr ""
...
...
@@ -3262,6 +3265,9 @@ msgstr ""
msgid "An error has occurred"
msgstr ""
msgid "An error in reporting in which a test result incorrectly indicates the presence of a vulnerability in a system when the vulnerability is not present."
msgstr ""
msgid "An error occurred adding a draft to the thread."
msgstr ""
...
...
@@ -29992,6 +29998,9 @@ msgstr ""
msgid "The file name should have a .yml extension"
msgstr ""
msgid "The finding is not a vulnerability because it is part of a test or is test data."
msgstr ""
msgid "The following %{user} can also merge into this branch: %{branch}"
msgstr ""
...
...
@@ -30294,6 +30303,12 @@ msgstr ""
msgid "The visualization will appear in this tab when the CI/CD configuration file is populated with valid syntax."
msgstr ""
msgid "The vulnerability is known, and has not been remediated or mitigated, but is considered to be an acceptable business risk."
msgstr ""
msgid "The vulnerability is known, and has not been remediated or mitigated, but is considered to be in a part of the application that will not be updated."
msgstr ""
msgid "The vulnerability is no longer detected. Verify the vulnerability has been fixed or removed before changing its status."