From 38d7f8cc3c230f2890f667f7983366178ef1a729 Mon Sep 17 00:00:00 2001 From: DonNateR Date: Thu, 5 Nov 2020 14:48:30 -0600 Subject: [PATCH 1/2] Add short descriptions for each cases connector --- docs/cases/cases-ui-integrations.asciidoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/cases/cases-ui-integrations.asciidoc b/docs/cases/cases-ui-integrations.asciidoc index 6ca1f8f037..121ae9be3a 100644 --- a/docs/cases/cases-ui-integrations.asciidoc +++ b/docs/cases/cases-ui-integrations.asciidoc @@ -2,11 +2,11 @@ [role="xpack"] == Configuring external connections -You can push {es-sec} cases to these third-party systems: +You can push {es-sec} cases to these third-party systems and set the: -* {sn} -* Jira (including Jira Service Desk) -* {ibm-r} +* {sn}: Urgency, severity, and impact. +* Jira (including Jira Service Desk): Issue type (except epics), priority, and parent issue for subtasks. +* {ibm-r}: Issue type and severity To push cases, you need to create a connector, which stores the information required to interface with an external system. @@ -63,6 +63,7 @@ field is overwritten. ** `Comments`: Mapped to the {sn} `Comments` field. When a comment is updated in a Security case, a new comment is added to the {sn} incident. * For Jira issues: +** `Issue type`: Mapped to the Jira `Issue Type` field. This can be set to `Task`, `Story`, `Bug`, or `Subtask` (requires a parent issue). ** `Title`: Mapped to the Jira `Summary` field. When an update to a Security case title is sent to Jira, the existing Jira `Summary` field is overwritten. From 929c384b78af3126580ad69c1bd428b35a348396 Mon Sep 17 00:00:00 2001 From: DonNateR Date: Fri, 6 Nov 2020 12:29:29 -0600 Subject: [PATCH 2/2] Add short description of ibm-r incident types --- docs/cases/cases-ui-integrations.asciidoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/cases/cases-ui-integrations.asciidoc b/docs/cases/cases-ui-integrations.asciidoc index 121ae9be3a..f8e1437d37 100644 --- a/docs/cases/cases-ui-integrations.asciidoc +++ b/docs/cases/cases-ui-integrations.asciidoc @@ -6,7 +6,7 @@ You can push {es-sec} cases to these third-party systems and set the: * {sn}: Urgency, severity, and impact. * Jira (including Jira Service Desk): Issue type (except epics), priority, and parent issue for subtasks. -* {ibm-r}: Issue type and severity +* {ibm-r}: Incident type and severity To push cases, you need to create a connector, which stores the information required to interface with an external system. @@ -62,6 +62,7 @@ Security case description is sent to {sn}, the existing {sn} `Description` field is overwritten. ** `Comments`: Mapped to the {sn} `Comments` field. When a comment is updated in a Security case, a new comment is added to the {sn} incident. + * For Jira issues: ** `Issue type`: Mapped to the Jira `Issue Type` field. This can be set to `Task`, `Story`, `Bug`, or `Subtask` (requires a parent issue). ** `Title`: Mapped to the Jira `Summary` field. When an update to a @@ -72,7 +73,9 @@ Security case description is sent to Jira, the existing Jira `Description` field is overwritten. ** `Comments`: Mapped to the Jira `Comments` field. When a comment is updated in a Security case, a new comment is added to the Jira incident. + * For {ibm-r} issues: +** `Incident type`: Mapped to the {ibm-r} `Incident type` field, which includes all default and custom incident types supported by {ibm-r}. If an indicent type is hidden in {ibm-r}, it will not be hidden in a Security case. ** `Title`: Mapped to the {ibm-r} `Name` field. When an update to a Security case title is sent to {ibm-r}, the existing {ibm-r} `Name` field is overwritten. @@ -103,4 +106,4 @@ TIP: You can also configure which connector is used for each case individually .. Select the required connector from the `Incident management system` list. . To update an existing connector: .. Click `Update `. -.. Update the connector fields as required. \ No newline at end of file +.. Update the connector fields as required.ship \ No newline at end of file