-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Lens] Add more Lens QA doc #105057
[Lens] Add more Lens QA doc #105057
Conversation
Pinging @elastic/kibana-app (Team:KibanaApp) |
docs/user/dashboard/lens.asciidoc
Outdated
@@ -319,7 +319,12 @@ You can also change the index pattern for a single *Layer*. | |||
[[why-my-field-x-is-missing-from-the-fields-list]] | |||
===== Why is my field X missing from the fields list? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this just Why is my field missing from the list of fields?
When I read field X
, I think x-axis
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see X
as generic term, but I see what you mean. Will remove it.
docs/user/dashboard/lens.asciidoc
Outdated
*Lens* does not support the visualization of full-text fields, therefore it is not showing them in the data summary. | ||
If your field is not in the `Available fields` list in *Lens* there may be multiple reasons, here described: | ||
* the field is a full-text field, therefore it is not showing in the data summary. | ||
* the field is a Geo field, therefore it is not showing in the data summary prior to v.7.14.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is best practice to avoid calling out versions in the docs because it is hard to maintain. If there are version-specific docs, we only push PRs to those specific versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is about why fields do not appear in the Available fields list, so I'm not sure we need to include information about data summaries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is Geo field
correct? I'm not familiar with Maps, but is this the terminology they use?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is about why fields do not appear in the Available fields list, so I'm not sure we need to include information about data summaries.
You are right. Prior to 7.14 is wasn't showing up in the Available fields
, not data summaries
docs/user/dashboard/lens.asciidoc
Outdated
If your field is not in the `Available fields` list in *Lens* there may be multiple reasons, here described: | ||
* the field is a full-text field, therefore it is not showing in the data summary. | ||
* the field is a Geo field, therefore it is not showing in the data summary prior to v.7.14.0 | ||
* the mapping is not supported by index-patterns, for instance for fields in `flattened` objects |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Data analysts are unfamiliar with the concept of mapping. This statement is more for admins.
I would reword this statement so that it applies to analysts, or remove it.
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* 📝 Add more Lens qa doc * 🐛 Fix wrong ref * 🔥 Remove section anchor for now * Apply suggestions from code review Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> * 👌 Integrated feedback Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
* 📝 Add more Lens qa doc * 🐛 Fix wrong ref * 🔥 Remove section anchor for now * Apply suggestions from code review Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> * 👌 Integrated feedback Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Summary
More on #81780
Expanded the
missing field
answer based on previous PR, and added new question about datatable text styling.Not sure about releasing with 7.14. You think it's ok @KOTungseth ?
Checklist
Delete any items that are not applicable to this PR.
For maintainers