Skip to content

[Cases] Expose maximumCasesToOpen parameter in case action connection#247990

Merged
janmonschke merged 11 commits intoelastic:mainfrom
janmonschke:cases/max-cases-to-open-rule-config
Jan 23, 2026
Merged

[Cases] Expose maximumCasesToOpen parameter in case action connection#247990
janmonschke merged 11 commits intoelastic:mainfrom
janmonschke:cases/max-cases-to-open-rule-config

Conversation

@janmonschke
Copy link
Copy Markdown
Contributor

@janmonschke janmonschke commented Jan 6, 2026

Summary

Addresses https://github.com/elastic/security-team/issues/15196

image

Adds a new setting to the cases action that allows to configure the maximum amount of cases to open per rule run. The default was 5 before and it can be configured to be anything between 1 and 20 now.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

@janmonschke janmonschke added backport:skip This PR does not require backporting release_note:feature Makes this part of the condensed release notes Team:Cases Security Solution Cases team labels Jan 6, 2026
@janmonschke janmonschke marked this pull request as ready for review January 7, 2026 09:16
@janmonschke janmonschke requested a review from a team as a code owner January 7, 2026 09:16
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-cases (Team:Cases)

Copy link
Copy Markdown
Contributor

@christineweng christineweng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM!

  • When I changed the number to 0, it does not prevent me from enabling the rule. It will fail but I think it can be avoided, like how the time window validation work
image
  • Optional is probably not true anymore, if i remove 5, clicking enable and create rule will also throw an error
image
  • Maybe mentioned the maximum is 20?

Copy link
Copy Markdown
Contributor

@christineweng christineweng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! 🎉

@janmonschke
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #5 / cases security and spaces enabled: basic Common migrations migrations 7.11.1 -> latest stack version "before all" hook for "adds rule info to only alert comments for 7.12"

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
cases 1.4MB 1.4MB +499.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
cases 144.3KB 145.0KB +698.0B

History

@janmonschke janmonschke merged commit 0ad2a8a into elastic:main Jan 23, 2026
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:feature Makes this part of the condensed release notes Team:Cases Security Solution Cases team v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants