[Enhancement] Event Filter Name should be truncated and a tooltip should be displayed for the same.

[muskangulati-qasource]

In continuation with #101376

Describe the feature:
Event Filter Name should be truncated and a tooltip should be displayed for the same.

Describe a specific use case for the feature:

• Trusted App Tab:
  

• Event Filter Tab:
  

[elasticmachine]

Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt)

[manishgupta-qasource]

Reviewed & Assigned to @kevinlog

[ghost]

Hi @kevinlog

We tested this ticket on the latest 7.15.0-BC5 environment & found that the issue still exist . Please find below the testing details:

Build Details:

Build Details:
VERSION: 7.15.0-BC5
BUILD: 43957
COMMIT: 0239ff6864dd9930cfe9bcd9a679272f2b7465c2
ARTIFACT: https://staging.elastic.co/7.15.0-edd09abf/summary-7.15.0.html

Screen-Recording:

Administration.-.Kibana.-.Google.Chrome.2021-09-08.18-36-58.mp4

Let me know if you need more information on this.
Thanks!!

[kevinlog]

@samratbhadra-qasource can you give more details on how you got the cards to look the way they do? Did you put a lot of leading spaces in front of the Event filter name?

[kevinlog]

cc @dasansol92 - can you take a look when you get a chance? We can fix this for 7.15.1

[dasansol92]

@kevinlog Following this comment, I think we decided to let this as it is since the cards in Trusted apps and Event filters are different and are going to be unified with the new artifact card (when adding artifacts by policy). Let me know if this needs to be done before that.

[kevinlog]

got it, thanks for the refresher @dasansol92 .

I want to understand how @samratbhadra-qasource produced the look of the cards in the video first, then we can reprioritize or just close this with the intention of introducing Event Filters by Policy soon with the new card.

[ghost]

Hi @kevinlog No, I haven't entered any leading spaces in front of the Event filter name.

[dasansol92]

Oh, now I see how it looks in the video. So weird... This seems a regression from this commit.
It was fixed (it looked like this) in this pr

[dasansol92]

@kevinlog I think this is old and can be closed as is covered with the new artifacts card design, thoughts?
cc: @muskangulati-qasource

[muskangulati-qasource]

Hi @kevinlog,

We tested this ticket & found that the issue is Fixed on the 7.16.0-BC5 build. Please find below the testing details:

Build Details:

Kibana version: 7.16.0 BC5
Build: 46061
Commit: f13296db8798dd0cd39ab6cc4a61a35a2a2b05cc
Artifact page: https://staging.elastic.co/7.16.0-4d61fd94/summary-7.16.0.html

Screenshot:

Hence, closing this ticket and marking it as "Validated".

Thanks!