[SIEM] [CASES] Status / Batch update

[XavierM]

Summary

Cases API works:

• add a global status (open/closed) count
• add status (open/closed) count with find and filters
• rename state to status
• allow batch update for cases

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/siem (Team:SIEM)

[stephmilovic]

This is awesome @XavierM. You even added some new tests, hooray! I performed a code review, endpoint testing, and UI testing. I only came up with a couple of UI issues listed below. I published my Postman API docs with the endpoints and curl calls. We should make a new PR that has curl scripts like the detection engine for testing. https://documenter.getpostman.com/view/172706/SW7c2SuF?version=latest

While I was hard strapped to find issues with the code, I did find a couple of bugs in the UI. The first one is my fault and I can fix in a follow up PR.

I'm sure it was like this before and I didn't notice... but when we add a comment, we probably should refetch the whole case instead of appending the comment to the list, because the case version number isn't getting updated resulting in this bug.

The other one is the case count in the header isn't getting updated when a case is closed in the table. This one I put on you, although I am happy to help fix or to fix it myself in a new PR. Let me know what you think and I'm just about ready to LGTM :)

[XavierM]

This is awesome @XavierM. You even added some new tests, hooray! I performed a code review, endpoint testing, and UI testing. I only came up with a couple of UI issues listed below. I published my Postman API docs with the endpoints and curl calls. We should make a new PR that has curl scripts like the detection engine for testing. https://documenter.getpostman.com/view/172706/SW7c2SuF?version=latest

While I was hard strapped to find issues with the code, I did find a couple of bugs in the UI. The first one is my fault and I can fix in a follow up PR.

I'm sure it was like this before and I didn't notice... but when we add a comment, we probably should refetch the whole case instead of appending the comment to the list, because the case version number isn't getting updated resulting in this bug.

The other one is the case count in the header isn't getting updated when a case is closed in the table. This one I put on you, although I am happy to help fix or to fix it myself in a new PR. Let me know what you think and I'm just about ready to LGTM :)

Let me fix them, so it is over!!!

[XavierM]

@stephmilovic Like we discussed in the next PR we are going to move the comment in the case saved object. So I do not think we should take the time to fix it now. But for sure in the next PR I will make sure that we are good.
And add the reporters' functionality lie we discussed so we should be good.

please let me know

[stephmilovic]

Great work as usual @XavierM, LGTM 🚀 🎸

[XavierM]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 4bda96c

History

• 💚 Build #32950 succeeded ae629fb
• 💚 Build #32638 succeeded 04ea915
• 💚 Build #32617 succeeded 54a3caf
• 💔 Build #32307 failed 3516f06

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream