From d4952410609d77e2af8c6cbf4c0dc8d5b6c3e73c Mon Sep 17 00:00:00 2001
From: Alison Goryachev <alisonmllr20@gmail.com>
Date: Tue, 25 May 2021 20:04:41 -0400
Subject: [PATCH] update breaking changes template to incorporate ES
 deprecations

---
 .github/ISSUE_TEMPLATE/v8_breaking_change.md | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/v8_breaking_change.md b/.github/ISSUE_TEMPLATE/v8_breaking_change.md
index 67d2ee2d3286b..9361cf7a52b65 100644
--- a/.github/ISSUE_TEMPLATE/v8_breaking_change.md
+++ b/.github/ISSUE_TEMPLATE/v8_breaking_change.md
@@ -13,7 +13,8 @@ assignees: ''
 ****************************************
  
 Please add a team label to denote the team that the
-breaking change is applicable to.
+breaking change is applicable to. If the work requires
+changes to Upgrade Assistant itself, please tag Team:Elasticsearch UI.
  
 -->
 
@@ -23,6 +24,10 @@ breaking change is applicable to.
 
 8.0
 
+**Is this a Kibana or Elasticsearch breaking change?**
+
+<!-- Kibana breaking changes can be registered via the Kibana deprecations service. Elasticsearch breaking changes may require custom logic in Upgrade Assistant and assistance from the Elasticsearch UI team. See more details below. -->
+
 **Describe the change. How will it manifest to users?**
 
 **How many users will be affected?**
@@ -30,7 +35,9 @@ breaking change is applicable to.
 <!-- e.g. Based on telemetry data, roughly 75% of our users will need to make changes to x. -->
 <!-- e.g. A majority of users will need to make changes to x. -->
 
-**Can the change be registered with the [Kibana deprecation service](https://github.com/elastic/kibana/blob/master/docs/development/core/server/kibana-plugin-core-server.deprecationsservicesetup.md)?**
+**Are there any edge cases?**
+
+**[For Kibana deprecations] Can the change be registered with the [Kibana deprecation service](https://github.com/elastic/kibana/blob/master/docs/development/core/server/kibana-plugin-core-server.deprecationsservicesetup.md)?**
 
 <!-- The deprecation service is consumed by the Upgrade Assistant to surface Kibana deprecations.
   It provides a way for Kibana deprecations to be resolved automatically via an API
@@ -39,8 +46,11 @@ breaking change is applicable to.
 <!-- Each plugin owner is responsible for registering their deprecations via the service.
   Please link to the issue/PR that will add this functionality. -->
 
-**Are there any edge cases?**
+**[For Elasticsearch deprecations] Can the Upgrade Assistant make the migration easier for users? Please explain the proposed solution in as much detail as possible.**
+
+<!-- Upgrade Assistant consumes the ES deprecation info API to surface deprecations to users. In some cases, Upgrade Assistant can provide a way to resolve a particular deprecation returned from the API. Examples include: reindexing an old index, removing deprecated index settings, upgrading or deleting an old Machine Learning model snapshot. -->
 
+<!-- Please provide a detailed explanation on how you foresee the proposed "fix" to work, e.g., "The deprecation will be surfaced via XXX message in the deprecation info API. Upgrade Assistant can call XXX API to resolve this deprecation". See https://github.com/elastic/kibana/issues/91879 as a real-world example. -->
 ## Test Data
 
 <!-- Provide test data. We can’t build a solution without data to test it against. -->