---
title: "Create a Jira issue - Cluster"
slug: "create-a-jira-issue-cluster"
updated: 2025-03-10T14:38:41Z
published: 2025-03-10T14:38:41Z
canonical: "docs.hunters.ai/create-a-jira-issue-cluster"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Jira issue - Cluster

This recipe will trigger whenever a cluster is created on Hunters, creating a corresponding Jira issue in your Jira instance. This will help you keep your Jira service desk project updated and synced with the Hunters SOC platform.

> [!NOTE]
> 📘**Note**
> 
> This process requires Jira admin permissions. Make sure you have those enabled before starting.

**To create a Jira issue for a cluster:**

****Step 1: Set up Jira****

****1. Create custom fields****

> [!NOTE]
> 📘 **Note**
> 
> This process requires Jira admin permissions. Make sure you have those enabled before starting.

1. From your Jira settings, select **Issues**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira Admin settings - Issues.png)
2. From the left-side menu, navigate to **Custom fields** and then click **Create custom field**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira Admin settings - Custom fields.png)
3. Create the following custom fields:

| Field name | Type | Values |
| --- | --- | --- |
| Cluster UUID | Short text |  |
| Detector | Short text |  |
| Leads in cluster | Number |  |
| Lead UUID | Short text |  |
| Link to cluster | Short text |  |
| Incident Statistic | Short text (Read only) |  |
| Investigation state | Select list (Single choice) | Initial In progress Ignored Completed |

****2. Create a Jira project****

1. Open Jira and navigate to **Projects > Create project**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - new project.png)
2. From the project templates list, select **Service management** and then select **Blank project**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - blank project.png)
3. On the next page click on **Create blank project**.
4. Under Project type, select a company-managed project and finalize the project creation.

****3. Create a request type and assign fields****

1. From your new project, navigate to **Project settings**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira project settings.png)
2. Now, navigate to **Request types > Create request type > Create blank**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Create request type(1).png)
3. Create a new request type with the following details and then click **Add**:
  - **Name** - Incident
  - **Portal group** - General
  - **Issue type** - Task ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Create Incident request.png)
4. Add the following custom fields to the Incident request type by dragging and dropping them from the right-side **Fields** panel, and click on **Save changes**:

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Assign fields to request.png)
  - Link to cluster
  - Cluster UUID
  - Detector
  - Leads in cluster
5. Navigate to the **Issue view** tab and drag and drop the **Incident Statistic** field into the Description fields section. Then click on **Save changes**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Issue view.png)
6. From your project settings, navigate to **Issue types** and click **Sub-task**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Issue type subtasks.png)
7. Change the view to **Fields** view and scroll all the way down the list. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Subtask fields view2.png)
8. From the **Select field…** dropdown list, select the following fields to add them to the Sub-task:
  - Detector
  - Lead UUID
  - Investigation state

****4. Create Jira automation****

1. From your new project, navigate to **Project settings**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira project settings.png)
2. Now, navigate to **Automation** and click on **Create rule**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Automation create rule.png)
3. Click **Rule details** and name the rule **Statistics Calculation**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Name rule.png)
4. Click the trigger step to return to the rule setup. Search for and select the **Issue updated** trigger and then click **Next**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Statistics calculation rule trigger step(3).png)
5. Now, add the following steps to the automation in this order:

| Operator | Action | Details |
| --- | --- | --- |
| THEN | Lookup Issue | **JQL**: `parent = {{issue.key}}` |
| AND | Create Variable | **Variable name**: `TotalIssues` **Smart value**: `{{lookupIssues.size}}` |
| AND | Lookup Issue | **JQL**: `parent = {{issue.key}} and Status = Open` |
| AND | Create Variable | **Variable name**: `OpenIssues` **Smart value**: `{{lookupIssues.size}}` |
| AND | Lookup Issue | **JQL**: `parent = {{issue.key}} and Status = WIP` |
| AND | Create Variable | **Variable name**: `WIPIssues` **Smart value**: `{{lookupIssues.size}}` |
| AND | Lookup Issue | **JQL**: `parent = {{issue.key}} and Status = Done` |
| AND | Create Variable | **Variable name**: `DoneIssues` **Smart value**: `{{lookupIssues.size}}` |
| AND | Edit Issue | **Field**: Incident Statistic **Value**: `Total : {{TotalIssues}} \| Open : {{OpenIssues}} \| WIP : {{WIPIssues}} \| Done : {{DoneIssues}}` |
6. Turn on the rule.
7. From your project menu, select **Queues > All open**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - queues.png)
8. From the queue menu, click **Edit queue**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - Edit queue.png)
9. Under the Filter by section, click **More + > Request Type > Incident**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - queue filter add request type field.png)
10. Under Columns, add the **Leads in cluster** column and click **Save**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Jira - add column.png)

****Step 2: Set up Hunters****

****1. Open the required template****

1. From the Hunters menu, navigate to **Workflows > Workflow Manager**. ![image.png](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image%28237%29.png)
2. Under **Projects**, navigate to **Automated Workflows > Jira**. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Sync Hunters status recipe - Jira folder.png)
3. Locate the **Create a formatted issue in Jira - Cluster** recipe, click on the **…** menu and then select **Clone**. This will ensure you don’t override the template so you can use it again in the future. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Clone template.png)
4. Rename the recipe and click **Edit**.

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Rename and Edit.png)

****2. Connect your Hunters account****

> [!NOTE]
> 💡**Tip**If you’ve already connected Hunters to a recipe before, you can simply select the connection from the list and skip to the next step.  
>   
> ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Skip Hunters connection.png)

1. Follow [these](https://docs.hunters.ai/apidocs/manage-api-tokens) guidelines to create a Hunters API token with a **Customer** role (or higher).
2. Copy the **Client ID** and **Client secret** provided in the token creation process.
3. Navigate back to the recipe and click the **Trigger** step to edit it. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Trigger step.png)
4. On the right side panel, name your connection and paste the **Client ID** and **Client secret** in the appropriate fields. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image.png)
5. Select your **Region** based on the region set up for you upon Hunters tenant creation.
6. Click **Connect**.

****3. Connect your Jira account****

> [!NOTE]
> 💡**Tip**If you’ve already connected Jira to a recipe before, you can simply select the connection from the list and skip to the next step.  
>   
> ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Skip Jira connection.png)

1. From the recipe flowchart click **step 3** (“Search issues by JQL in Jira”) to connect the Jira account relevant to this process.
2. On the right-side panel, name your connection, select an **Authentication type** and complete the required authentication details. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Sync Hunters status recipe - Connect to Jira.png)
3. Click **Connect**.
4. In the **JQL query string** field, replace the **project** value with the name of the Jira project you created in the previous steps, and update the "cluster uuid" field to match the corresponding custom field you created.

> [!NOTE]
> 💡**TIP**
> 
> These fields are case sensitive and should be identical to the values from your Jira project.

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Jira JQL string.png)

****4. Connect your Jira Service Desk account****

1. From the recipe flowchart click **step 6** (“Create customer request in jira Service desk”) to connect the Jira Service account relevant to this process.
2. Complete the connection information (similar to the previous step), and click **Connect**.

After establishing the connection, more fields will appear.
3. From the **Service Desk** field, select the project you’ve created in the previous steps.
4. From the **Request type** field, select **Incident**.

> [!NOTE]
> 💡**TIP**
> 
> Even if the fields are already filled with the correct value, delete it and reselect the value.

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6.png)
5. Scroll down to the **Request** section and open the available optional fields. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6 - Request section.png)
6. From the available fields select the below fields and click **Apply changes**:
  - Link to cluster
  - Cluster UUID
  - Detector ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6 - select optional fields.png)
7. Fill in the fields with data from Step 1 of this workflow:
  1. Click the field’s text box and then click **Recipe Data** to open the data selection popup. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6 - Select from data.png)
  2. Search for the required value from the data gathered in step 1 and click to add it. ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6 - Select data pill.png) By the end of this process, you should achieve the following mapping:

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 6 - field mapping.png)
    - **Link to cluster** = Threat link
    - **Cluster UUID** = Threat UUID
    - **Detector** = Detector Title

****5. Finalize workflow settings****

1. From the recipe flowchart click **step 8** (“Create issues in Jira”).
2. Edit the fields as follows:
  - **Project issue type** - `Your project name : Sub-task`. For instance, `CSOC : Sub-task`
  - **Sample project issue type** - `Your project name : Sub-task`. For instance, `CSOC : Sub-task`
3. Make sure your other fields are set up as in this image: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 8.png)
4. From the recipe flowchart click **step 9** (“Update issues in Jira”).
5. From the **Sample project issue type** field, select `your project name : Task` .
6. Make sure your other fields are set up as in this image: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create Jira issue from cluster - Step 9.png)

****6. Save and activate the recipe****

1. Once done, click **Save** and then **Exit**.  
  
![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/Create email recipe from template - Save and exit.png)
2. Now click **Start recipe** to activate the workflow.  
  
![image.png](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image%28130%29.png)