github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update breaking changes issue template (#95787)

Browse source
This commit is contained in:
Alison Goryachev 2021-04-01 08:58:48 -04:00 • committed by GitHub
parent 7fe316562d
commit b29ccdcac1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

20
.github/ISSUE_TEMPLATE/v8_breaking_change.md vendored
View file

@ -2,7 +2,7 @@
name: 8.0 Breaking change
about: Breaking changes from 7.x -> 8.0
title: "[Breaking change]"
labels: Team:Elasticsearch UI, Feature:Upgrade Assistant, Breaking Change
labels: Feature:Upgrade Assistant, Breaking Change
assignees: ''
---
@ -12,8 +12,8 @@ assignees: ''
******* LABEL CHANGES NECESSARY ********
****************************************
Please add a "NeededFor:${TeamName}" label to denote the team that is
requesting the breaking change to be surfaced in the Upgrade Assistant.
Please add a team label to denote the team that the
breaking change is applicable to.
-->
@ -30,16 +30,14 @@ requesting the breaking change to be surfaced in the Upgrade Assistant.
<!-- 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. -->
**How can we programmatically determine whether the cluster is affected by this breaking change?**
**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)?**
**What can users do to address the change manually?**
<!-- 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
or manually by providing step-by-step instructions for users to follow. -->
<!-- If applicable, describe the manual migration steps and/or link to available docs. -->
**How could we make migration easier with the Upgrade Assistant?**
<!-- This can be as basic as notifying the user about the deprecation and linking to some
migration docs, or as advanced as a dedicated UI for fixing the problem. -->
<!-- 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?**