Description
Description
We are introducing a new property in cases, called incremental id. Think of it as an easy-to-read identifier for cases. Referencing cases by their uuid in conversations is complicated, so we're adding a more readable id. Similar to the ids you see on Github issues.
This incremental id is assigned in the background at a given interval (default: 10 minutes, see config below) and will not be immediately available after case creation. It cannot be set by the user. When a case is exported, the id will be removed. Users can find cases by their incremental id from the search field in the cases list by searching for #123.
TBD: We're waiting for a go/no-go for 8.19/9.1. This ticket is written as if there was a GO.
Config
xpack.cases.incrementalId.enabled: Enables/disables the feature (default: true)
xpack.cases.incrementalId.taskIntervalMinutes: The interval the task should run at in minutes (default: 10, minimum: 5)
xpack.cases.incrementalId.taskStartDelayMinutes: The delay at which the service should start processing after Kibana started (default: 10, minimum: 1).
Advanced settings
cases:incrementalIdDisplay:enabled: Enables/disables the display of incremental ids in the cases UI (default: true)
Screenshots
(Note: Design pending)
The new ID in the cases table
The new ID in the case details page
Searching for cases by their incremental ID
Background & resources
- PRs: [Cases] Add incremental id service and expose the ID in the UI kibana#222874
- Issues/metas: [Investigations][Cases] - Cases Incremental Numeric Identifier kibana#212570
- Point of contact: @janmonschke
- Test environments: (TBD)
Which documentation set does this change impact?
ESS and serverless
ESS release
The functionality will be introduced in ESS 8.19 and 9.1
Serverless release
Unknown
Feature differences
The feature is identical in ESS and serverless
API docs impact
(TBD)
Prerequisites, privileges, feature flags
No response