1. Introduction

This article describes the Vulcan-Jira workflow for Vulcan users, so our and Jira Admin users can set a smooth workflow for issues generated by Vulcan.

The article summarizes information for a comprehensive understanding of our Jira automation:

  1. Introduction

  2. Connecting the Jira connector

  3. Setting a Vulcan-Jira issue closing workflow

  4. What is the information generated from Vulcan into JIRA ticket?

  5. Choosing the 'Done' option

  6. FAQ

2. Connecting the Jira connector

In order to connect a Jira account to Vulcan, please use our Connectors page. You will find a Jira widget containing all the information needed.

Click here for a detailed article about this connection.

After you connect, you can access the Jira connector's Advanced configurations, where you will be able to define default values for your Jira issues.

3. Setting a Vulcan-Jira issue closing workflow

In order to create a Jira workflow that works smoothly and securely, you will need to pay attention to a few details:

  • Vulcan sets a label 'vulcan_generated' to every issue created in Jira;

  • Vulcan allows you to define what is the desired 'Done' status for each Playbook, or for each Campaign;

  • Vulcan will use the first available 'Open' status in your list (this is not configurable).

  • Vulcan sets the issue Reporter as the Admin user that connected the account.

You will have to create a transition that allows Vulcan to close tickets from Open>Done using rules that limit other users and issues from being moved the same way. The suggested rules are:

  1. The issue must have a label 'vulcan_generated'

  2. The issue must have a reporter that equals the same person who activated the Vulcan connection

See an example below:

4. What is the information generated from Vulcan into JIRA ticket?

Click here for a complete article explaining how the Jira issues will look like.

5. Choosing the 'Done' option

In the Playbook and Campaign Jira forms, you will find a 'Mark issues as done' toggle option, which is enabled by default. When enabled, a mandatory drop-down will give users a choice to opt for an option that is within the 'Done' status category.

6. FAQ

Does the user need to configure anything in Jira?

Yes, they do have to configure status transitions that allow Vulcan to close the tickets.

Does Vulcan support ‘in progress’ status in Jira?

No, we do not. Jira admins need to configure Vulcan-specific transitions in their Jira environment, using our label vulcan_generated and limiting users that can report.

What is a ‘Done’ status category in Jira and why do users need to choose one of them in Vulcan?

It is the final stage of the issue lifecycle and usually is used to define what was the issue resolution. Examples of ‘Done’ statuses are: Resolved, Rejected, Duplicated, etc. In Vulcan, users may want to mark issues as ‘Done’ when vulnerabilities related to a given Vulcan-generated Jira ticket were fixed, and the meaning would be ‘Resolved’ in this case.

Did this answer your question?