[Security Solution] All detection rules cannot be selected with one operation - limited to 300 max

[MikePaquette]

Describe the bug:

• Users need to repeat bulk operations on rules if the number of rules exceeds 300, causing extra work, and risk of inconsistent operations.

Kibana/Elasticsearch Stack version:

• 7.11.0 BC1

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

• Detection rules
• Rule management

Preconditions:

• None

Steps to reproduce:

1. Navigate to Security > Detections
2. Click on Manage detection rules button

Current behavior:

• User can check the checkbox next to "Rules" to select all rules currently in rules table.
• The number of rows in the rules table is limited to 300
• The number of prebuilt rules exceeds 300
• Result is that the user must repeat any bulk operation multiple times when number of rules exceeds number of table rows.
• This causes extra work on the detection engineer, causing frustration.

Expected behavior:

• User needs some way to select all rules in rules table

Errors in browser console (if relevant):
None

Errors in browser console (if relevant):
None

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

Any additional context:

• Condition was present in 7.10 when prebuilt rules exceeded 300

Screenshots (if relevant):

Errors in browser console (if relevant):
None

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

[MikePaquette]

@MadameSheema I think this is higher priority, and should be treated like a bug, since it causes the analyst/rule_author to perform extra work, causes frustration, and can introduce errors. Can we get this fixed in 7.11.0?

[MadameSheema]

@spong @peluja1012 can we tackle this issue on 7.11?

[peluja1012]

PR here #87410

[MadameSheema]

Lots of thanks for the fix @peluja1012 ❤️