[Security Solution] The long rule name breaks the UI structure under exception tab in rule details page

[ghost]

Describe the bug
The long rule name breaks the UI structure under exception tab in rule details page

Build Details:
Version:7.16.0 BC5
Build: 46061
COMMIT: f13296d

Browser Details:
N/A

Preconditions

1. Kibana should be running
2. Rule should be created with long name
3. Alerts should be generated from created rule

Steps to Reproduce

1. Navigate to Alerts tab of security tab
2. Click on more action icon of generated alerts
3. Add the rule exception
4. Navigate to rule details page and click on exception tab
5. Observe that long rule name breaks the UI structure under exception tab in rule details page

Actual Result
The long rule name breaks the UI structure under exception tab in rule details page

Expected Result
UI should not be break with long rule name under exception tab in rule details page

What's Working

• N/A

What's Not Working

• N/A

Screen-Shots

Rule Name with Space:

Rule Name Without Space:

[elasticmachine]

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

[MadameSheema]

@deepikakeshav-qasource can you please try to reproduce the same with a long rule name but with spaces on it? Thanks

[ghost]

Hi @MadameSheema ,

Yes, Issue is also occurring with long rule name with spaces. I have also shared the observations in bug as well.

Please let us know if anything else is required from our end.

Thanks!!

[spong]

Here's an issue covering other remaining max-length and overflow issues between the Rule Creation, Edit, and Details pages: #119402

[spong]

@jethr0null -- users are running into this issue in the discuss forums, so we should prioritize accordingly. Fix is low impact and low LOE, so can probably bundle in with the other overflow issues outlined in #119402 and tackle post-FF for 8.1.

[jethr0null]

Thanks for flagging this. cc @peluja1012 for scheduling consideration

[yctercero]

PR merged, backports running now!

[MadameSheema]

@deepikakeshav-qasource can you please validate this on 8.1.0BC3? Thanks :)

[ghost]

Hi @MadameSheema ,

We have validated this issue on 8.1.0 BC3 build. and found that issue is fixed.

Build Details:

Version: 8.1.0-BC3
Commit:0335dd6a26ef29ae9021d0fae9347dc88f3b7d6e
Build:50346

Screenshots

Hence, we are closing this issue and marking as QA Validated.

Thanks!

[ghost]

Hi @MadameSheema

We have validated this issue on 8.0.1 BC1 and found it still Fixed. ✔️

Please find below the testing details:

Build Details:

Version: 8.0.1
Commit: f4b44d7eb7355c9d1e38d9f2dc753b3fe10c601c
Build: 49342

Screenshot:

Thanks !!