Jira Integration

Flyingduck supports seamless integration with Jira, enabling you to automatically create and track issues from security findings directly within your Jira projects. This streamlines collaboration and ensures vulnerabilities are triaged and resolved efficiently.

Access the Integration

1. Sign in to the Flyingduck portal as an administrator.
2. In the sidebar, go to Administration → Integrations → Notifications.
3. Under Jira, click Integrate.

Configure Jira Integration

1. Enter Jira Domain

   • Provide your Jira domain URL (e.g., https://your-domain.atlassian.net).

2. Enter Authentication Details

   • Enter the email address associated with your Jira account and API token.
   • Generate an API token from your Jira account via the Atlassian API Token page (opens in a new tab), then paste it here.

3. Test Authentication

   • Click Test Authentication to validate the credentials.
   • Once verified, Flyingduck will establish the connection with your Jira workspace.

With Jira successfully integrated, your development and security teams can collaborate more effectively by managing vulnerabilities directly within Jira.

Once the integration with Jira is successfully established, Flyingduck will maintain a secure connection with your Jira instance. Through this connection, users can manage security issues and create Jira tickets in two ways:

1. Manual Ticket Creation Users can create Jira tickets individually for each security issue. This allows precise control over which issues are reported and how they are categorized in Jira.

2. Automated Ticket Creation Users can enable automation to streamline the ticket creation process. With automation, Flyingduck can automatically generate Jira tickets for multiple issues based on predefined rules or events, reducing manual effort and ensuring timely tracking of all relevant findings.

Manual Jira Ticket Creation

Flyingduck allows users to create Jira tickets manually for individual security issues, giving precise control over which issues are reported and how they are tracked. Users can create tickets directly from Flyingduck, and the tickets will be automatically created in Jira without any additional actions required within Jira. This ensures seamless and efficient issue reporting, eliminating the need to log into Jira or perform separate steps.

How to Create a Jira Ticket

From the Global Issues or Commit Findings page, select the issue you want to report. Click ... --> Create Jira Ticket to open the ticket creation dialog.

Fields to Complete:

• Project Name: Select the Jira project for the ticket.
• Priority: Set the urgency: Highest, High, Medium, or Low.
• Issue Type: Choose the Jira issue type (Bug, Task, Story).
• Reporter & Assignee: (Optional) — Select both the reporter and the assignee for the ticket. if not selected, the assignee will be set to None.
• Summary: (Optional) — Provide a short title for the issue.
• Description: (Optional) — Add detailed information to help triage and resolve the issue.
• Create: Submit the ticket to Jira using the provided Summary as the ticket name and Description as the ticket details.

Why Manual Ticket Creation

• Ensures only selected issues are reported.
• Allows precise control over project, priority, issue type, reporter, and assignee.
• Useful for high-priority or sensitive issues that need careful handling.

Jira Automation

Flyingduck allows users to automate Jira ticket creation using Jira Templates and Workflows. This ensures consistent ticket creation, reduces manual effort, and improves tracking of security issues.

Accessing the Automation

To configure Jira automation, navigate to the Automation page from the sidebar. This page provides access to both Jira Template and Workflow setup for automated ticket creation and notifications.

Jira Template

The Jira Template screen lets users create and manage reusable templates that define the key parameters for automated ticket creation.

• To create a new Jira template: click Jira Template → Create New.

Fields

• Template Name: Enter a unique name to identify your template.
• Template Description: Provide a short description explaining the template’s purpose.

Jira Ticket Details

• Jira Project: Select the Jira project where tickets created using this template will be sent.

• Jira Issue Type: Choose the type of Jira issue (Bug, Task, Story).

• Save: Store the template for future automated use.

Purpose Creating a Jira template ensures that tickets are consistently generated with the correct project and issue type, saving time and maintaining standardization for frequently reported issues.

Workflow

The Workflows screen defines how Jira templates are applied and allows automation of ticket creation and notifications based on repositories, issue types, and severities.

• To create a new workflow: click Workflows → Create New.

Fields

• Workflow Name: Enter a name for the workflow.
• Workflow Description: Provide a brief description of the workflow’s purpose.
• Repositories: Select one or more repositories where this workflow should apply.
• Issue Types: Choose which types of issues trigger the workflow.
• Severity: Select severity levels to include (Critical, High, Medium, Low).

Notification Timers

• Notification Channel: Choose a Jira template from the available templates.
• Save: Save the workflow and activate automation.

Purpose Workflows ensure that Jira templates are applied automatically according to defined criteria, enabling consistent ticket creation, automated notifications, and improved incident response across projects and repositories.