From e94e176067fb187b81d429d66fdbe05f71cb0f5e Mon Sep 17 00:00:00 2001
From: mtsuji-cobalt <102162593+mtsuji-cobalt@users.noreply.github.com>
Date: Wed, 25 Oct 2023 08:28:07 -0400
Subject: [PATCH] Create push-findings-to-azure-devops-boards.md

---
 .../push-findings-to-azure-devops-boards.md   | 43 +++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 content/en/Integrations/Azure DevOps/push-findings-to-azure-devops-boards.md

diff --git a/content/en/Integrations/Azure DevOps/push-findings-to-azure-devops-boards.md b/content/en/Integrations/Azure DevOps/push-findings-to-azure-devops-boards.md
new file mode 100644
index 000000000..531f29bad
--- /dev/null
+++ b/content/en/Integrations/Azure DevOps/push-findings-to-azure-devops-boards.md	
@@ -0,0 +1,43 @@
+---
+title: "Push Findings to Azure DevOps Boards"
+linkTitle: "Push Findings to Azure DevOps Boards"
+weight: 50
+description: >
+  Once you’ve connected your Azure DevOps instance, you can configure pentests to push findings to an ADO Team Project.
+---
+
+## Configure the Integration for a Pentest
+
+Once you’ve connected your Azure DevOps instance, configure the integration for specific pentests.
+
+1. In Cobalt, go to **Integrations** > **Azure DevOps Boards** > **Configuration**. Here, you can see pentests for which you can configure the integration.
+2. For the desired pentest, select the gear icon.
+3. For the “Create tickets for findings” sync, click **Edit**.
+4. In the workflow editor overlay that appears, configure the integration parameters:
+- Open the “Create Work Item in Azure DevOps” action.
+- Select values for the required (*) parameters: **Project, Work Item Type, Title, State**. New work items created for findings in this pentest will be based on these selections.
+- Provide values for any other required fields in your work item template. Required fields will be marked with a red asterisk (*).
+- Set values for any other optional fields. If a field in your work item template is not visible in the form, click “Show optional fields” at the top of the input form, and select the appropriate fields from the list.
+5. Click **Save** in the workflow editor to save your entries.
+6. Close the workflow editor by clicking **Done**.
+7. To enable sync for the pentest, activate the toggle for “Create tickets for findings".
+
+## Update Configuration for a Pentest
+
+To modify the configuration for a pentest: 
+
+1. In Cobalt, go to **Integrations** > **Azure DevOps Boards** > **Configuration**. 
+2. For the desired pentest, select the gear icon.
+3. For the “Create tickets for findings” sync, if the sync is enabled (indicated by a blue switch), disable it by clicking the switch so that it displays in gray.
+4. For the “Create tickets for findings” sync, click **Edit**.
+5. Follow the steps in [Configure the Integration for a Pentest](tbd) to change configuration options.
+
+## Deactivate Integration for a Pentest
+
+You can manage Azure DevOps connections for specific pentests:
+
+1. View the connection status in **Integrations** > **Azure DevOps Boards** > **Configuration**. 
+2. Beside a pentest with Azure DevOps integration enabled (where the Status indicator is green), select the gear icon.
+3. For any sync that is enabled (indicated by a blue switch), disable it by clicking the switch so that it displays in gray.
+4. Click the back arrow icon to return to the list.
+5. The Status indicator will now display in gray.