From ab0dd39a49e43f6beed9bdb6414a0f04bcf671b4 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 21 Jan 2020 06:09:08 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/user/analytics/cycle_analytics.md | 9 +++++++++ doc/user/project/operations/error_tracking.md | 9 +++++++-- 2 files changed, 16 insertions(+), 2 deletions(-) (limited to 'doc/user') diff --git a/doc/user/analytics/cycle_analytics.md b/doc/user/analytics/cycle_analytics.md index dfc0f488ff9..e0bb4e03c41 100644 --- a/doc/user/analytics/cycle_analytics.md +++ b/doc/user/analytics/cycle_analytics.md @@ -163,6 +163,15 @@ This chart uses the global page filters for displaying data based on the selecte group, projects, and timeframe. In addition, specific stages can be selected from within the chart itself. +### Chart median line + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/36675) in GitLab 12.7. + +The median line on the chart displays data that is offset by the number of days selected. +For example, if 30 days worth of data has been selected (for example, 2019-12-16 to 2020-01-15) the +median line will represent the previous 30 days worth of data (2019-11-16 to 2019-12-16) +as a metric to compare against. + ### Enabling chart By default, this chart is disabled for self-managed instances. To enable it, ask an diff --git a/doc/user/project/operations/error_tracking.md b/doc/user/project/operations/error_tracking.md index 361dfe57d78..3fcf6e39ee0 100644 --- a/doc/user/project/operations/error_tracking.md +++ b/doc/user/project/operations/error_tracking.md @@ -55,6 +55,7 @@ This page has: - A link to the Sentry issue. - A link to the GitLab commit if the Sentry [release id/version](https://docs.sentry.io/workflow/releases/?platform=javascript#configure-sdk) on the Sentry Issue's first release matches a commit SHA in your GitLab hosted project. - Other details about the issue, including a full stack trace. +- In [GitLab 12.7 and newer](https://gitlab.com/gitlab-org/gitlab/issues/36246), language and urgency are displayed. By default, a **Create issue** button is displayed. Once you have used it to create an issue, the button is hidden. @@ -78,6 +79,10 @@ Ignoring an error will prevent it from appearing in the [Error Tracking List](#e ### Resolving errors -From within the [Error Details](#error-details) page you can resolve a Sentry error by simply clicking the **Resolve** button near the top of the page. +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/39825) in GitLab 12.7. -Marking an error as resolved indicates that the error has stopped firing events. If another event occurs, the error reverts to unresolved. +From within the [Error Details](#error-details) page you can resolve a Sentry error by +clicking the **Resolve** button near the top of the page. + +Marking an error as resolved indicates that the error has stopped firing events. If another event +occurs, the error reverts to unresolved. -- cgit v1.2.3