---
title: "Map Cobalt Pentest Finding Severity to Jira Issue Priority"
description: "This guide is designed to help Integration Builder users map the severity of pentest findings in Cobalt to the priority of new Jira issues. Please follow the Create Jira tickets for Findings guide before proceeding with this guide."
canonical_url: "https://docs.cobalt.io/articles/map-cobalt-pentest-finding-severity-to-jira-issue-priority-0NcIxLIYOW"
md_url: "https://docs.cobalt.io/articles/map-cobalt-pentest-finding-severity-to-jira-issue-priority-0NcIxLIYOW.md"
---
# Map Cobalt Pentest Finding Severity to Jira Issue Priority

:::info
This guide is designed to help [Integration Builder](https://docs.cobalt.io/en-us/articles/integration-builder-Aelp0wU7EI) users map the severity of pentest findings in Cobalt to the priority of new Jira issues. Please follow the [Create Jira tickets for Findings guid](https://docs.cobalt.io/en-us/articles/create-jira-tickets-for-findings-5iy1QEDBuE)e before proceeding with this guide.

:::

## **Basic Option**


1. Navigate to the **\[Cobalt > Jira Cloud\] Push pentest finding to Jira** recipe that you set up while [following the previous guide](https://docs.cobalt.io/en-us/articles/create-jira-tickets-for-findings-5iy1QEDBuE).
2. Open the edit view for the recipe by clicking the **Edit** button.
3. Find the **Create Jira Issue** action in the recipe and click on it.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=985e6928-d632-40db-b1f7-8214db4785d1)


4. In the pane that opens on the right, scroll down until you see the **Issue Priority** field. Click into the dropdown so that you can see the options that are displayed. Take note of them, you will need them later.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=142e39b2-b6db-4ab6-963f-1f830d53259c)


5. Hover your cursor above the **Monitor** block that encapsulates the **Create issue in Jira** action. An **Add step** button will appear. Click on it.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=d416f00e-9166-474c-a390-1cdfb381b8d2)


6. Choose the **Action in app** option.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=b711a0a5-95eb-434b-8ffe-667440909603)


7. Search for **variable** in the connector search bar. Select the **Variables by Workato** connector.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=b022e03b-a39a-4223-9aba-786a0bb3f7c1)


8. Select the **create variable** action.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=3ed96d16-ee90-4fa8-b61b-50093a05ed6b)


9. Click the **Add a variable** button.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=f31e87e6-04c5-442b-b919-6bda0c604107)


10. Name the variable `jira_issue_priority`and click **Add variable**.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=3cfdd356-02b7-46e0-8bf2-d166c9e39ece)


11. Below the **create variable** action that you added, add a new step with the **if condition** type.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=8aebe290-9026-4e12-be01-79008110cf97)


12. Click on the **if condition** that you created so that the configuration pane opens on the right. Once it opens, click the **data field** input.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=05657a10-e732-497f-be75-4d2ee6fa148d)


13. In the recipe data drawer, find the **Get pentest finding** action. Use the arrow to the right of the action to see all of its output fields. Select the **Severity** field.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=4c90eb2c-8874-43ea-b94a-3df38876abbf)


14. In the if condition configuration pane, click the **condition** input field and choose the **equals** option.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=a38fd001-55ef-43fe-a44a-21a829a7b02a)


15. In the **value** input field, enter the Cobalt finding severity that you want to map to a Jira issue priority. You can find all Cobalt finding severities listed [here](https://docs.cobalt.io/en-us/articles/findings-D4kEiuzfAW#h-get-all-findings).

 ![](https://docs.cobalt.io/api/attachments.redirect?id=235f9c02-3aa4-4566-ac02-1a4c572bfb82)


16. Click on the empty action slot nested under the **if condition**. In the configuration pane that opens on the right, click the **Variables by workato** connector.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=e90731ce-1458-4b77-881d-4440b715deb7)


17. Select the **update variables** action.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=bcdc29fc-68d2-466d-a860-9f2bbec0e2ec)


18. In the **variable name** input field, select the `jira_issue_priority`variable that you created earlier.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=50e0e3c5-c1aa-4b45-baa8-621f3d961c5a)


19. In the `jira_issue_priority`input field, enter the Jira issue priority that you want to map to the Cobalt finding severity that you set in the if condition. Type the priority exactly as you noted it earlier.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=78a312ca-8757-4885-a0e4-d56b8725e6b3)


20. Add more if conditions for each severity that you want to map to a Jira issue priority. You can add as many if conditions as you need.
21. Once you have added all the if conditions that you need, click the **Create issue in Jira** action in the recipe.
22. In the configuration pane on the right, scroll down until you see the **Issue priority** input field. Click on the dropdown that says **Select from list** and choose the **Use priority name** option.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=d3155cf4-0a51-4bf4-90dd-9e6b7242bcbb)


23. Map the `jira_issue_priority`variable that you created earlier to the **Issue priority** input field.

 ![](https://docs.cobalt.io/api/attachments.redirect?id=5d326229-8203-4c6a-a06f-276e24fa2a1a)  ![](https://docs.cobalt.io/api/attachments.redirect?id=e21b245e-3f6c-4237-b520-a82a4dd9cdde)


24. That’s it! Click save and start your recipe.

## **Advanced Option**

If you have multiple recipes that push pentest findings to Jira, you can create a reusable recipe that maps Cobalt finding severity to Jira issue priority. This way, you can use the same recipe in multiple places without having to recreate the mapping logic each time.

To learn more, [check out this documentation](https://docs.workato.com/connectors/recipe-functions.html) from our integrations technology partner.