diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-17 21:09:08 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-17 21:09:08 +0300 |
| commit | 6b922f9bb0a09fa74565a45e4af324d0324adba9 (patch) | |
| tree | d2a1677ba2047c0b2c15560544c2181432befbc7 /doc/user/project/operations | |
| parent | c61d90dbfa0a7cb58b758ed07a9d0b5406beb61e (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/operations')
| -rw-r--r-- | doc/user/project/operations/alert_management.md | 12 | ||||
| -rw-r--r-- | doc/user/project/operations/feature_flags.md | 8 | ||||
| -rw-r--r-- | doc/user/project/operations/img/alert_list_sort_v13_1.png | bin | 0 -> 13919 bytes |
3 files changed, 20 insertions, 0 deletions
diff --git a/doc/user/project/operations/alert_management.md b/doc/user/project/operations/alert_management.md index 411b36411af..b93d7c6fd7c 100644 --- a/doc/user/project/operations/alert_management.md +++ b/doc/user/project/operations/alert_management.md @@ -64,6 +64,18 @@ Each alert contains the following metrics: - **Event count** - The number of times that an alert has fired. - **Status** - The [current status](#alert-management-statuses) of the alert. +### Alert Management list sorting + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/217745) in GitLab 13.1. + +The Alert Management list displays alerts sorted by start time, but you can +change the sort order by clicking the headers in the Alert Management list. + +To see if a column is sortable, point your mouse at the header. Sortable columns +display an arrow next to the column name, as shown in this example: + + + ### Alert Management statuses Each alert contains a status dropdown to indicate which alerts need investigation. diff --git a/doc/user/project/operations/feature_flags.md b/doc/user/project/operations/feature_flags.md index a9729204cd7..f9ef33f628c 100644 --- a/doc/user/project/operations/feature_flags.md +++ b/doc/user/project/operations/feature_flags.md @@ -146,6 +146,14 @@ CAUTION: **Caution:** The Unleash client **must** be given a user ID for the feature to be enabled for target users. See the [Ruby example](#ruby-application-example) below. +#### List + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/35930) in GitLab 13.1. + +A feature flag can be enabled for lists of users created with the [Feature Flag User List API](../../../api/feature_flag_user_lists.md). +Similar to [User IDs](#user-ids), it uses the Unleash [`userWithId`](https://unleash.github.io/docs/activation_strategy#userwithid) +activation strategy. + ## Integrate feature flags with your application To use feature flags with your application, get access credentials from GitLab. diff --git a/doc/user/project/operations/img/alert_list_sort_v13_1.png b/doc/user/project/operations/img/alert_list_sort_v13_1.png Binary files differnew file mode 100644 index 00000000000..8e06c3478f7 --- /dev/null +++ b/doc/user/project/operations/img/alert_list_sort_v13_1.png |
