Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add short descriptions for each cases connector #348

Closed
wants to merge 2 commits into from
Closed

Add short descriptions for each cases connector #348

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38d7f8c
Add short descriptions for each cases connector
narcher7 Nov 5, 2020
929c384
Add short description of ibm-r incident types
narcher7 Nov 6, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions docs/cases/cases-ui-integrations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}: Incident type and severity

To push cases, you need to create a connector, which stores the information
required to interface with an external system.
Expand Down Expand Up @@ -62,7 +62,9 @@ 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
Security case title is sent to Jira, the existing Jira `Summary` field is
overwritten.
Expand All @@ -71,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.
Expand Down Expand Up @@ -102,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 <connector name>`.
.. Update the connector fields as required.
.. Update the connector fields as required.ship