From 8f2cb58b700a369f48b728dccafe652a187dc319 Mon Sep 17 00:00:00 2001
From: Tim Sullivan <tsullivan@users.noreply.github.com>
Date: Mon, 3 May 2021 10:44:04 -0700
Subject: [PATCH] Reporting/Docs: update version of reporting_user deprecation
 (#98988) (#99085)

---
 docs/settings/reporting-settings.asciidoc | 4 ++--
 docs/user/reporting/index.asciidoc        | 2 +-
 docs/user/security/reporting.asciidoc     | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/settings/reporting-settings.asciidoc b/docs/settings/reporting-settings.asciidoc
index 084ac633e9bc..70f3e272fa5a 100644
--- a/docs/settings/reporting-settings.asciidoc
+++ b/docs/settings/reporting-settings.asciidoc
@@ -276,14 +276,14 @@ For information about {kib} memory limits, see <<production, using {kib} in a pr
   setting. Defaults to `.reporting`.
 
 | [[xpack-reporting-roles-enabled]] `xpack.reporting.roles.enabled`
-  | deprecated:[7.13.0,This setting must be set to `false` in 8.0.] When `true`, grants users
+  | deprecated:[7.14.0,This setting must be set to `false` in 8.0.] When `true`, grants users
   access to the {report-features} by assigning reporting roles, specified by `xpack.reporting.roles.allow`. 
   Granting access to users this way is deprecated. Set to `false` and use
   {kibana-ref}/kibana-privileges.html[{kib} privileges] instead.
   Defaults to `true`.
 
 | `xpack.reporting.roles.allow`
-  | deprecated:[7.13.0,This setting will be removed in 8.0.] Specifies the roles,
+  | deprecated:[7.14.0,This setting will be removed in 8.0.] Specifies the roles,
   in addition to superusers, that can generate reports, using the {ref}/security-api.html#security-role-apis[{es} role management APIs].
   Requires `xpack.reporting.roles.enabled` to be `true`.
   Granting access to users this way is deprecated. Use
diff --git a/docs/user/reporting/index.asciidoc b/docs/user/reporting/index.asciidoc
index 144ed1ea28c9..9e4271b3659b 100644
--- a/docs/user/reporting/index.asciidoc
+++ b/docs/user/reporting/index.asciidoc
@@ -32,7 +32,7 @@ for different operating systems.
 == Roles and privileges
 
 When security is enabled, access to the {report-features} is controlled by security privileges. In versions 7.12 and earlier, you can grant access to the {report-features}
-by assigning users the `reporting_user` role in {es}. In 7.13 and later, you can configure *Reporting* to use
+by assigning users the `reporting_user` role in {es}. In 7.14 and later, you can configure *Reporting* to use
 <<kibana-privileges, {kib} privileges>>. It is recommended that *Reporting* is configured to
 use {kib} privileges by setting <<xpack-reporting-roles-enabled,`xpack.reporting.roles.enabled`>> to `false`. By using {kib} privileges, you can define
 custom roles that grant *Reporting* privileges as sub-features of {kib} applications in *Role Management*.
diff --git a/docs/user/security/reporting.asciidoc b/docs/user/security/reporting.asciidoc
index 2f331e252c49..ab25dddd0469 100644
--- a/docs/user/security/reporting.asciidoc
+++ b/docs/user/security/reporting.asciidoc
@@ -17,7 +17,7 @@ For more information, see
 
 [[reporting-app-users]]
 Access to reporting features is limited to privileged users. In older versions of Kibana, you could only grant
-users the privilege by assigning them the `reporting_user` role in Elasticsearch. In 7.13 and above, you have
+users the privilege by assigning them the `reporting_user` role in Elasticsearch. In 7.14 and above, you have
 the option to create your own roles that grant access to reporting features using <<kibana-privileges, {kib} privileges>>.
 
 It is recommended that you set `xpack.reporting.roles.enabled: false` in your kibana.yml to begin using Kibana