Skip to main content

Jira Integration (Client Portal)

Cyver Core integrates with multiple ticket and work management platforms, so you can easily push tickets and findings to the tooling your Dev team uses. That makes it easier to move tickets into remediation, so you can quickly roll changes into sprints and fix them in the Cyver Core portal. 

 

Pentester Portal - Allow the client to connect Jira

The client can connect Jira to push tickets and status information by enabling the toggle into Clients > Open a client > Client Portal tab:

Client Portal - Link Cyver Core to Your Jira Account

1. Go to Settings from the left-hand menu.

2. Click Integrations.

3. Select Jira Cloud. 

4. Follow the steps to authorize Jira Cloud and grant the necessary permissions.

Your Jira Cloud account is now connected!

 5. Click Settings on the Jira Cloud tile to configure the integration.

Configuration

Within the Jira Settings pop-up, you can configure exactly how Cyver Core interacts with your Jira projects.

Sync to Jira

  • Push finding to Jira on publish: Enable this to automatically create a new Jira ticket whenever a finding is made visible (published) to a client.

    Once enabled, you must select the default Jira issue type (Task, Sub-task, Story, Bug, Epic) that will be created.

  • Auto-update Jira status: Enable this to automatically update the Jira ticket status when the Finding status changes in Cyver.

    You must map finding statuses (e.g., Pending Fix, Accepted) to the corresponding Jira statuses (e.g., In Progress, Done).

  • Push finding comments to linked Jira ticket: Enable this to send comments made in Cyver Core directly to the linked Jira ticket.

Sync from Jira

  • Sync Finding Status from Jira on Update: Enable this to update the Finding status in Cyver when the Jira ticket status changes.

    You must map your Jira statuses (e.g., Selected for Development, In Progress) to the corresponding finding statuses (e.g., Retest Requested, Accepted).

  • Sync finding comments from Jira: Enable this to import comments made in Jira back into the Cyver Finding.

Both these settings requires webhooks connection to be configured. Follow the instruction here for more.

Other Settings

  • Adjust Jira Project per Pentest: Enable this to allow selecting a different Jira project for each specific pentest instead of using one global project.

    • Parent Issue: If you are using a hierarchy, you can define a default Parent Issue for the tickets to be linked to.

  • Update linked finding in Jira on update: If enabled, changes to the finding fields in Cyver will update the Jira ticket content.

  • Field mappings: Enable this to map specific Cyver Finding fields to Jira fields. This ensures data lands in the right place.

    • Per Issue Type: You can configure unique mappings for each Jira issue type.

    • Available Fields: You can map finding fields to your Jira fields.

How to Configure Jira per Project

1. Open a project.

2. Click on Actions.

3. Click on Configure Jira.


 

4. Switch to another Jira Project from the list.

  1. Select a Parent Issue (optional). This allows you to link all findings from this pentest to a specific parent ticket in Jira.

  2. Click Save.

How to Create and Link Tickets

You can manually push findings to Jira or link them to existing tickets directly from the Finding view.

Create a New Jira Ticket

1. Open a Finding.

2. On the right-hand side panel, click Create Jira Ticket.

3. Select the Issue Type and Parent issue (if any).

4. Click Create Jira Ticket.

Link to an Existing Jira Ticket

1. Open a Finding.

2. Click Link to Existing Ticket. 

  1. In the search box, type the Jira ticket name to find the relevant issue.

  2. Select the ticket and click Save.

How to view the client Jira account configured from the Pentester Portal

Webhook Automation Configuration 

To enable status and comment syncing from Jira back to Cyver Core, you must configure automation rules in your Jira instance.

1. Sync Status Updates (Issue Update Webhook)

  1. Log in to your Jira account.
  2. Click the Settings (gear icon) in the top-right corner to open the menu, then select the System option.
  3. From the left-hand menu, select Global automation.
  4. In the top-right corner, click Create rule > Create from scratch.
  5. In the "Add a trigger" section, search for Work item transitioned, select it, and click Next.
  6. In the "Add a component" section, select THEN: Add an action.
  7. In the "Add an action" section, search for Send web request and select it.
  8. Configure the web request details:

a. Set the Web request URL to: https://connect.cyver.io/App/Integrations/JiraCloudWebhookEvent/IssueUpdated

b. Set the HTTP method to POST.

c. Set the Web request body to Issue data (Jira format).

d. Add a new header named X-API-Key with the value provided in your Cyver integration settings.

e. Click Next.

  1. Click Turn on rule.
  2. Name the rule (e.g., "Cyver Status Sync") and click Turn on rule to finish.

2. Sync Comments (Issue Commented Webhook)

  1. Log in to your Jira account.

  2. Click the Settings (gear icon) in the top-right corner to open the menu, then select the System option.

  3. From the left-hand menu, select Global automation.

  4. In the top-right corner, click Create rule > Create from scratch.

  5. In the "Add a trigger" section, search for Work item commented, select it, and click Next.

  6. In the "Add a component" section, select THEN: Add an action.

  7. In the "Add an action" section, search for Send web request and select it.

  8. Configure the web request details:

a. Set the Web request URL to: https://connect.cyver.io/App/Integrations/JiraCloudWebhookEvent/IssueCommentedOn

b. Set the HTTP method to POST.

c. Set the Web request body to Custom data and paste the following JSON code:

{
  "comment": {
    "id": "{{comment.id}}",
    "body": "{{comment.body.jsonEncode}}",
    "created": "{{comment.created}}",
    "updated": "{{comment.updated}}",
    "author": {
      "emailAddress": "{{comment.author.emailAddress}}",
      "displayName": "{{comment.author.displayName}}"
    }
  },
  "issue": {
    "id": "{{issue.id}}",
    "key": "{{issue.key}}",
    "status": "{{issue.status.name}}"
  },
  "project": {
    "id": "{{issue.project.id}}",
    "name": "{{issue.project.name}}"
  }
}

d. Add a new header named X-API-Key with the value provided in your Cyver integration settings.

e. Click Next.

  1. Click Turn on rule.

  2. Name the rule (e.g., "Cyver Comment Sync") and click Turn on rule to finish.

Was this article helpful?