TABLE OF CONTENTS

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)


General setup 

Step 1 - Finding the integration settings

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 - Connecting your Jira account

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. 

See Step 6 if you want to send ISMS.online items to Jira

See Step 8 if you want to receive Jira issues in ISMS.online


Step 6 - ISMS.online → Jira workflows

To send an IO Track Item to Jira, enable and configure the first workflow.

Tips

  • Jira Project and Issue type field→ Choose the Jira Project you want to create issues in, and choose the type of issue you want to create. 
  • Track Item status trigger→ Choose the item status that will trigger the creation of a Jira issue. 


In the example shown below, when an IO Track Item is updated to the status 'Assess - A.5.25', a Security Incident ticket will be created in the Incident Resolution project in Jira.

If all you want to do is send IO items to Jira when conditions are met, you can stop here.


Step 7

To close the loop on this automation, we can enable the second workflow to get an update back from the created Jira Issue.


Tips

  • Jira Project and Issue type field→ Choose the Jira Project you want to create issues in, and choose the type of issue you want to create.
  • Jira Project and Issue status trigger→ Pick the same Jira Project as above, and then choose the issue status to trigger the update back to IO.
  • Track Item status update→ Choose the Item status to set the IO item to, this is what gets updated by the Jira issue status trigger above.

In the example shown below, when a Security Incident in Jira is updated to the 'Done' status, the corresponding IO Track Item it was created from will be updated to the 'Resolved' status.


Step 8 - Jira → ISMS.online workflows

To send an issue from Jira to IO as a Track Item, we want to enable the 3rd workflow in the list.


Tips

  • Jira Project and Issue type → Choose the Jira Project you want the integration to focus on, and choose the type of issue that will be able to trigger item creation in IO.
  • Jira Issue status trigger → Choose the issue status that will trigger item creation in IO. Only issues that are updated to this status will trigger the automation.

In the example shown below, when a Security Incident in Jira is updated to the 'Escalate' status, an IO Track Item will be created using the Issues Summary and Description fields. You can choose any default Jira status, and also any custom statuses you may have setup.

If all you want to do is send Jira Issues to IO when conditions are met, you can stop here.


Step 9

To close the loop on this automation, we can enable the second workflow to send a status update back to the original Jira Issue.


Tips

  • Track Item status trigger → Choose the Item status in IO that will trigger the update back to Jira.
  • Jira Project and Issue status update → Choose the Jira Issue status to set the Issue to, this is what gets updated by the Track Item status trigger above.

In the example shown below, when a Track Item in IO is updated to the 'Resolved' status, the corresponding Jira Issue it was created from will be updated to the 'Done' status.


Final Step

Click X to close the integration settings, and the integration will be ready to work.


 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