[UA] Remove panel that links to logs explorer #201532
Assignees
Labels
chore
Feature:Upgrade Assistant
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Comments
jloleysens
added
chore
Feature:Upgrade Assistant
Team:Core
|
Pinging @elastic/kibana-core (Team:Core) |
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
|
Can we maybe change the width to hug the text rather than fit the width? So we keep the sentence in 1 line, but avoid extra white space on the right? |
|
tentatively self assigning |
2 tasks
4 tasks
jesuswr
added a commit
to jesuswr/kibana
that referenced
this issue
Dec 12, 2024
## Summary resolves elastic#201532 Removed the panel containing the logs explorer link. Updated tests and i18n. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit b059879) # Conflicts: # x-pack/platform/plugins/private/translations/translations/zh-CN.json
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Jan 13, 2025
## Summary resolves elastic#201532 Removed the panel containing the logs explorer link. Updated tests and i18n. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the upgrade assistant, we guide users to Elasticsearch's deprecation logs to help them address their usage of deprecated APIs. Today we guide them to "Logs Exploerer" and "Discover". We should only guide them to "Discover", i.e. remove the panel about "Logs explorer" entirely.
This is what the panel looks like today:
This is what it should look like, possibly without the surrounding panel
The text was updated successfully, but these errors were encountered: