-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Event Filter Name does not truncate on the UI #101376
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt) |
@manishgupta-qasource please review!! |
Reviewed & Assigned to @kevinlog |
@dasansol92 splitting the text as you have above looks good to me. As long as it doesn't overflow that we're OK. In addition, I think long names will be rare - as long as we're handling it in some way, then we're OK. @bfishel @caitlinbetz let me know if you think differently |
PR: #101481 |
Hi @kevinlog, We tested this ticket on the latest 7.14.0-SNAPSHOT build and the issue is now fixed. Query Build Details:
cc: @dasansol92 Thanks!! |
@muskangulati-qasource @kevinlog This is because the card component used in trusted apps is different than the ones used in event filters. We could unify those cards to be displayed in the same way but would need a coordination with the detections team as the event filters card is used for other exceptions |
Thanks for the insight @dasansol92 @muskangulati-qasource I think we can close this one as is and open an enhancement to unify the cards. @bfishel wanted to redesign them at some point in any case. |
Bug Conversion
Thanks! |
Describe the feature
Event Filter Name does not truncate on the UI
Build Details:
Preconditions
Steps to Reproduce
Test data
N/A
Impacted Test case(s)
N/A
Actual Result
Event Filter Name does not truncate on the UI
Expected Result
Event Filter Name should be truncated and wrapped on the UI
What's Working
N/A
What's Not Working
N/A
Screenshot
Logs:
N/A
The text was updated successfully, but these errors were encountered: