Skip to content

Commit 321502d

Browse files
[Cases][Serverless & 9.2]: Docs for incremental case IDs (elastic#3358)
Fixes elastic#3255 and elastic#1758 by explaining that cases are automatically assigned human-readable numeric IDs, which you can use for easier referencing. Also refreshed outdated images of the Cases table and removed case screenshots that weren't adding value and were outdated. Previews: - [Stack management cases](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3358/explore-analyze/alerts-cases/cases) - [Observability cases](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3358/solutions/observability/incident-management/cases) - [Security cases](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3358/solutions/security/investigate/cases)
1 parent eaa3c5d commit 321502d

File tree

10 files changed

+8
-26
lines changed

10 files changed

+8
-26
lines changed

explore-analyze/alerts-cases/cases.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ Cases are used to open and track issues directly in {{kib}}. You can add assigne
1515

1616
{applies_to}`stack: preview` {applies_to}`serverless: preview` You can also optionally add custom fields and case templates.
1717

18+
{applies_to}`stack: ga 9.2` Cases are automatically assigned human-readable numeric IDs, which you can use for easier referencing. Each time you create a new case in your [space](docs-content://deploy-manage/manage-spaces.md), the case ID increments by one. IDs are assigned to cases by a background task that runs every 10 minutes, which can cause a delay in ID assignment, especially in spaces with many cases. You can find the case ID after the case's name and can use it while searching the Cases table.
19+
1820
:::{image} /explore-analyze/images/kibana-cases-list.png
1921
:alt: Cases page
2022
:screenshot:
-4.26 KB
Loading
5.69 KB
Loading
-161 KB
Binary file not shown.
-9.11 KB
Loading
-403 KB
Binary file not shown.
-302 KB
Binary file not shown.

solutions/observability/incident-management/cases.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ navigation_title: Cases
1212

1313
Collect and share information about observability issues by creating a case. Cases allow you to track key investigation details, add assignees and tags to your cases, set their severity and status, and add alerts, comments, and visualizations. You can also send cases to third-party systems by [configuring external connectors](/solutions/observability/incident-management/configure-case-settings.md).
1414

15+
{applies_to}`stack: ga 9.2` Cases are automatically assigned human-readable numeric IDs, which you can use for easier referencing. Each time you create a new case in your [space](docs-content://deploy-manage/manage-spaces.md), the case ID increments by one. IDs are assigned to cases by a background task that runs every 10 minutes, which can cause a delay in ID assignment, especially in spaces with many cases. You can find the case ID after the case's name and can use it while searching the Cases table.
16+
1517
:::{image} /solutions/images/observability-cases.png
1618
:alt: Cases page
1719
:screenshot:

solutions/security/investigate/cases.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ navigation_title: Cases
1616

1717
Collect and share information about security issues by opening a case in {{elastic-sec}}. Cases allow you to track key investigation details, collect alerts in a central location, and more. The {{elastic-sec}} UI provides several ways to create and manage cases. Alternatively, you can use the [cases API](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-cases) to perform the same tasks.
1818

19+
{applies_to}`stack: ga 9.2` Cases are automatically assigned human-readable numeric IDs, which you can use for easier referencing. Each time you create a new case in your [space](docs-content://deploy-manage/manage-spaces.md), the case ID increments by one. IDs are assigned to cases by a background task that runs every 10 minutes, which can cause a delay in ID assignment, especially in spaces with many cases. You can find the case ID after the case's name and can use it while searching the Cases table.
20+
1921
You can also send cases to these external systems by [configuring external connectors](/solutions/security/investigate/configure-case-settings.md#cases-ui-integrations):
2022

2123
* {{sn-itsm}}

solutions/security/investigate/open-manage-cases.md

Lines changed: 2 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -45,12 +45,6 @@ Open a new case to keep track of security issues and share their details with co
4545
If you’ve selected a connector for the case, the case is automatically pushed to the third-party system it’s connected to.
4646
::::
4747

48-
49-
:::{image} /solutions/images/security-cases-ui-open.png
50-
:alt: Shows an open case
51-
:screenshot:
52-
:::
53-
5448
% Check with Lisa if email notifications is an ESS-only feature. Not in Serverless docs: https://www.elastic.co/guide/en/serverless/current/security-cases-open-manage.html
5549

5650
## Add email notifications [cases-ui-notifications]
@@ -82,11 +76,6 @@ When you subsequently add assignees to cases, they receive an email.
8276

8377
From the Cases page, you can search existing cases and filter them by attributes such as assignees, categories, severity, status, and tags. You can also select multiple cases and use bulk actions to delete cases or change their attributes. General case metrics, including how long it takes to close cases, are provided above the table.
8478

85-
:::{image} /solutions/images/security-cases-home-page.png
86-
:alt: Case UI Home
87-
:screenshot:
88-
:::
89-
9079
To explore a case, click on its name. You can then:
9180

9281
* [Review the case summary](/solutions/security/investigate/open-manage-cases.md#cases-summary)
@@ -119,12 +108,6 @@ Click on an existing case to access its summary. The case summary, located under
119108
* **In progress duration**: How long the case has been in the `In progress` state
120109
* **Duration from creation to close**: Time elapsed from when the case was created to when it was closed
121110

122-
:::{image} /solutions/images/security-cases-summary.png
123-
:alt: Shows you a summary of the case
124-
:screenshot:
125-
:::
126-
127-
128111
### Manage case comments [cases-manage-comments]
129112

130113
To edit, delete, or quote a comment, select the appropriate option from the **More actions** menu (****).
@@ -157,14 +140,7 @@ After adding events to cases from the Events table (which you can access from th
157140

158141
### Add files [cases-add-files]
159142

160-
To upload files to a case, click the **Files** tab:
161-
162-
:::{image} /solutions/images/security-cases-files.png
163-
:alt: A list of files attached to a case
164-
:screenshot:
165-
:::
166-
167-
You can set file types and sizes by configuring your [{{kib}} case settings](kibana://reference/configuration-reference/cases-settings.md).
143+
To upload files to a case, select the **Files** tab, then click **Add files**. You can set file types and sizes by configuring your [{{kib}} case settings](kibana://reference/configuration-reference/cases-settings.md).
168144

169145
% Check with Lisa whether following note is only applicable to Serverless or if it's for ESS too.
170146

@@ -326,4 +302,4 @@ To import a case:
326302
* If the imported case had connectors attached to it, you’ll be prompted to re-authenticate the connectors. To do so, click **Go to connectors** on the **Import saved objects** flyout and complete the necessary steps. You can also access connectors from the **{{connectors-ui}}** page (find **{{connectors-ui}}** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md)).
327303
* If the imported case had attached alerts, verify that the alerts' source documents exist in the environment. Case features that interact with alerts (such as the Alert details flyout and rule details page) rely on the alerts' source documents to function.
328304

329-
::::
305+
::::

0 commit comments

Comments
 (0)