-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FX-5213] Create docs for integrations 'Re-associate existing ticket'…
… functionality (#596)
- Loading branch information
1 parent
adff3f3
commit 43280ab
Showing
2 changed files
with
43 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
title: "Carried Over Findings" | ||
linkTitle: "Carried Over Findings" | ||
weight: 140 | ||
description: > | ||
Configure integration behavior for carried over findings | ||
--- | ||
|
||
### What is a Carried-Over Finding? | ||
|
||
When you conduct a pentest on an asset that still has unfixed findings from a previous pentest, pentesters can "carry over" the findings to the new pentest. | ||
When the pentester carries over the finding, the original finding's state will be set to "Carried Over". | ||
|
||
### Default Integration Behavior for Carried-Over Findings | ||
|
||
By default, ticketing integrations will treat carried over findings as new findings. | ||
This means that your integration will create a new ticket for the carried over finding regardless of the existence of a ticket for the original finding. | ||
|
||
### Avoid Creating New Tickets for Carried-Over Findings | ||
|
||
If you do not want your integration to create a new ticket for a carried-over finding when a ticket already exists for the original finding, | ||
you can configure your integration (at the pentest level) to use the alternative carry-over handling logic. | ||
If you would like to use the non-default carry-over handling logic, we recommend performing the following configuration steps before launching a new pentest: | ||
|
||
1. Navigate to the new pentest in the Cobalt UI | ||
2. Navigate to the Integrations tab | ||
3. In the "Ticket creation for carry over findings" tile, click the radio button for the "Re-associate existing ticket" option | ||
4. Click save | ||
|
||
{{% image src="/integrations/carry-over-findings/carryover-ticket-handling-config.png" alt="UI config option" %}} | ||
|
||
### What Does Re-associating the Existing Ticket Do? | ||
|
||
When the carried over finding is moved to the Pending Fix state, the following will happen: | ||
|
||
1. The ticket will be unlinked from the original finding | ||
2. The ticket will be linked to the carried over finding | ||
|
||
### Which Integrations Are Supported? | ||
|
||
* Native Jira Cloud integration | ||
* Native Jira Data Center (server) integration | ||
* Integration Builder External Ticket References |
Binary file added
BIN
+180 KB
static/integrations/carry-over-findings/carryover-ticket-handling-config.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.