Any Track in ISMS.online can be connected to Jira using the available workflows, each workflow can be enabled once per Track. See a demo of the integration here.

The Jira integration is capable of:

  1. Creating tickets in Jira when a track item changes to a specific status and

  2. Changing the status of the ISMS.online Track item when the Jira issue changes to a specific status.

Combined, this allows organisations to take something like a Security incident, send it to Jira to be resolved, and then receive a status update back when the ticket is complete.

Currently, the integration uses information from the Track item Name and Description fields to fill out the created Jira issue.

Examples of use cases for the integration are below:

  1. Incident Management: Send an incident to Jira when a track item reaches a specific status, and when the linked Jira ticket reaches a specific status, update the status of the incident item in ISMS.online.

  2. Technical Vulnerabilities: Send a new vulnerability to Jira to be resolved when the track item reaches a specified status. When the linked Jira ticket is resolved, update the status of the corresponding vulnerability item in ISMS.online.

  3. Corrective Actions: Send a corrective action to Jira when a track item reaches a specified status, when the linked Jira ticket is resolved, update the status of the corrective action in ISMS.online.



Key terms

Integration: An integration is the ability to connect to a service (e.g. Jira), within any one integration you can have multiple workflows enabled.

Workflow(s): These are the series of steps which sends or receives data between the integrated apps, an integration can have multiple workflows available to use e.g.

  • Workflow 1: Create a new Jira ticket when X happens

  • Workflow 2: Update a Jira ticket when Y happens

  • If a user enabled workflow 1, they can automate Jira ticket creation when something happens in ISMS.online. If they ALSO enable workflow 2, they can then receive an update back to ISMS.online if the Jira ticket gets updated. 



Who can use the integration?

To configure any native integration in Tracks, you must have:

  1. Permission to Administer the Track you want to integrate.

  2. A Jira user account & permissions to access the Jira Project you want to connect to.

  3. API access enabled for the user configuring the integration. This is because the integration needs to create an API key. (Organisation admins can grant this permission via user settings)


Setting up the Jira integration

Step 1

Integrations are configured in the Track Settings page.


Step 2

The Integrations panel will show which integrations are available. It also displays which integrations are enabled in this Track.


Step 3

Clicking to Connect with Jira will open the first step, which is authenticating your Jira account.



Step 4

Once authenticated, choose which instance of Jira to connect to, then click Finish.


Step 5

Now we can enable workflows to get the integration to start working. To create Track items in Jira you must choose a Project to create the Jira issue in, and the issue type to create.


Step 6

Then, enable the second workflow to receive an update when the Jira issue reaches a specific status. Choose the same Jira Project and Issue type as in step 4. In the example, we are configuring it so that Jira will send an update back to ISMS.online when the Jira issue changes to the ‘Done’ status. After this, you can close the pop-up to reach the next step.


Final step

To finish set up, configure the ISMS.online side. You can choose which Track item status should trigger the creation of a Jira issue, after that you configure the update that is sent back, by picking a status to change the Track Item to when our Jira issue status is changed to ‘Done’. 


Click Finish, and the integration will be ready to work.

Through following these steps we have set up an integration that will…

  • create a Jira ticket associated to a Track item that has the ‘Respond’ status right arrow 

  • and when the Jira ticket is completed, the ISMS.online Track Item will be updated to the ‘Resolved’ status. right arrow curving left 

Now, you can send your assessed incidents to Jira for response, when the incident ticket in Jira is complete, the original Track item for the incident will be updated to the Resolved status.


 Question Answer
I purchased integrations but cannot see them in my Track settings page?
Users can only use integrations if they have the ‘Generate API key permission’ granted by an Organisational admin. See here for details on this step.
I chose the Jira ticket type ‘Subtask’ for my integration, but it’s not working?

Select a different ticket type for the integration to work.


Jira Subtasks may appear in the Issue type dropdown field, this ticket type is not supported by the integration due to restrictions within Jira.


How do I check the statuses I chose to trigger my integration workflows?
Edit the integration again to see the settings to check which statuses have been selected to trigger the Jira integration.
How do I disable part of the integration from working?
Click the toggle button on a workflow to enable or disable it. Blue workflow toggles are enabled, and Grey ones are disabled.
How do I disconnect my integration completely?
Edit the integration in Track Settings, scroll down and click the red Disconnect button. This will erase settings for all configured workflows.
I enabled both workflows but it’s not working when I try to trigger the integration?

If you have followed all of the steps provided, but your integration still isn’t working- check the following:


Jira Project and Issue type is the same for all choices 


The right ISMS.online status is being used to trigger the workflow. 


If you’re still encountering issues, please contact our support team: support@isms.online