Skip to content
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

[Security Solution] When adding a field to Timeline Template, width is too small to see entire field name #126083

Closed
MikePaquette opened this issue Feb 21, 2022 · 5 comments · Fixed by #141084
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Timeline Security Solution Timeline feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team

Comments

@MikePaquette
Copy link

Kibana version: 8.1.0 BC1

Elasticsearch version: 8.1.0 BC1

Server OS version: Elastic Cloud ESS default

Browser version: Google Chrome Version 98.0.4758.102 (Official Build) (x86_64)

Browser OS version: macOS Monterey Version 12.2.1 (21D62)

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud ESS GCP Europe-West-1

Describe the bug:
When adding a field to Timeline Template, width is too small to see entire field name

Steps to reproduce:

  1. Edit a Timeline or Tempate
  2. Attempt to add a field with a long name
  3. Notice that you can't see the entire field name, causing the analyst to guess at what it is.

Expected behavior:
Should be able to see the entire field name.

Screenshots (if relevant):
image

Errors in browser console (if relevant): None

Provide logs and/or server output (if relevant): N/A

Any additional context: None

@MikePaquette MikePaquette added bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Timeline Security Solution Timeline feature labels Feb 21, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@michaelolo24
Copy link
Contributor

@monina-n thoughts on how we may want to approach fixing this. I think the current behavior is to rely on a tooltip

@MindyRS MindyRS added the Team:Threat Hunting Security Solution Threat Hunting Team label Feb 23, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@monina-n
Copy link

In general the width of the popover (and subsequently the dropdown) should be increased and that should account for a majority of use cases. If after we increase width, it's still not enough we can talk about other options

@logeekal
Copy link
Contributor

Please see if new layout makes sense. This solves the width problem without any customization.

Old Layout New Layout
image image

logeekal added a commit that referenced this issue Sep 22, 2022
Fixes: #126083

Changed the layout of the Add Field popover so that field `Field` can have full width and users can see long index properties without any issue.

Please see if new layout makes sense. This solves the width problem without any customization.
|Old Layout| New Layout|
|--|--|
|![image](https://user-images.githubusercontent.com/7485038/191256799-b38b4e23-6bb0-492d-8908-bf63eeb7994c.png)|![image](https://user-images.githubusercontent.com/7485038/191256474-77263af3-e593-46a9-a31e-be54a9518f45.png)|
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Sep 22, 2022
Fixes: elastic#126083

Changed the layout of the Add Field popover so that field `Field` can have full width and users can see long index properties without any issue.

Please see if new layout makes sense. This solves the width problem without any customization.
|Old Layout| New Layout|
|--|--|
|![image](https://user-images.githubusercontent.com/7485038/191256799-b38b4e23-6bb0-492d-8908-bf63eeb7994c.png)|![image](https://user-images.githubusercontent.com/7485038/191256474-77263af3-e593-46a9-a31e-be54a9518f45.png)|

(cherry picked from commit 2b4fc2e)
kibanamachine added a commit that referenced this issue Sep 22, 2022
Fixes: #126083

Changed the layout of the Add Field popover so that field `Field` can have full width and users can see long index properties without any issue.

Please see if new layout makes sense. This solves the width problem without any customization.
|Old Layout| New Layout|
|--|--|
|![image](https://user-images.githubusercontent.com/7485038/191256799-b38b4e23-6bb0-492d-8908-bf63eeb7994c.png)|![image](https://user-images.githubusercontent.com/7485038/191256474-77263af3-e593-46a9-a31e-be54a9518f45.png)|

(cherry picked from commit 2b4fc2e)

Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Timeline Security Solution Timeline feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants