[Cases] Add the ability to filter cases by date in the find and status endpoints

[cnasikas]

Summary

This PR

• Extends the find cases endpoint to accept a date range by introducing the from and to query parameters.
• Extends the status cases endpoint to accept a date range by introducing the from and to query parameters.
• Exposes from the UI cases client two functions to find cases and get the statuses. Usage:

const { cases } = useKibana().services;

const allCases = cases.api.cases.find({
    status: 'open',
      from: 'now-1w',
      to: 'now'
    }
  });

const casesStatuses = cases.api.cases.getAllCasesMetrics({
    status: 'open',
      from: 'now-1w',
      to: 'now'
    }
  });

Closes: #128483

API usage

Find cases: /api/cases/_find?status=closed&from=now-1w&to=now
Get status: /api/cases/status?from=now-1M&to=now-1w

Docs Preview

https://kibana_128652.docs-preview.app.elstc.co/guide/en/kibana/master/cases-api-find-cases.html

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

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

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[academo]

It all looks good to me though I have a remark: we are not testing error paths, when a malformed date is sent to the endpoint.

Can you add tests to cover those cases?

[cnasikas]

It all looks good to me though I have a remark: we are not testing error paths, when a malformed date is sent to the endpoint.

Can you add tests to cover those cases?

Thanks, Esteban! I do in multiple places. For example here: https://github.com/elastic/kibana/pull/128652/files#diff-bbb2457715292047ff5e11bf70e6a6e560c2674d3dd2548cdcdd54fb45efa705R524. Do you have something else in mind?

[academo]

It all looks good to me though I have a remark: we are not testing error paths, when a malformed date is sent to the endpoint.
Can you add tests to cover those cases?

Thanks, Esteban! I do in multiple places. For example here: #128652 (files). Do you have something else in mind?

Does it make any difference if you test more incorrect formats? If you feel this is enough then let's go with it.

[cnasikas]

It all looks good to me though I have a remark: we are not testing error paths, when a malformed date is sent to the endpoint.
Can you add tests to cover those cases?

Thanks, Esteban! I do in multiple places. For example here: #128652 (files). Do you have something else in mind?

Does it make any difference if you test more incorrect formats? If you feel this is enough then let's go with it.

I think is fine because I mostly need to check if I catch the error correctly. I think by testing incorrect formats I will start testing the kibana core framework and in turn ES. Do you have any specific format in mind?

[cnasikas]

@elasticmachine merge upstream

[cnasikas]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: fb60640
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Page load bundle

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

id	before	after	diff
cases	86.2KB	86.3KB	+181.0B

History

• 💔 Build #35124 failed a7f13ea
• 💛 Build #34772 was flaky 9fc34a1
• 💚 Build #34554 succeeded 14d0978
• 💔 Build #34535 failed 14c36fd
• 💔 Build #34129 failed fa753a1cdb69ccb3cb3c4b30d6b6a7ed0e85346b

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

cc @cnasikas