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.

The Jira integration supports two workflow directions - most users will only need to make use of one:

  1. IO Track → Jira: This workflow handles cases where work that started in a Track needs to continue in Jira. A Track Item reaching a selected status (e.g. In Progress) creates a new Jira issue; when that issue is updated to another selected status (e.g. Resolved), the Track Item will receive a status update as well.

  2. Jira → IO Track: This workflow handles cases where work that started in Jira needs to continue in an IO Track. A Jira issue reaching a selected status (e.g. Escalated) creates a new Track Item in IO; when that item is updated to another selected status (e.g. Resolved), the Jira issue will receive a status update as well.

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: When an incident is raised in ISMS.online, automatically send it to your engineering or IT team's Jira backlog for investigation — and receive the status update back once it's resolved, keeping your audit trail complete.

  2. Technical Vulnerabilities & Corrective Actions: Push Vulnerabilities or Actions directly into Jira so technical teams can work in their existing tools, while compliance teams can see the status update in IO.

  3. Custom Tracks: Many organisations build custom Tracks to manage other compliance or business processes — supplier reviews, change requests, access control approvals, and more. If your process involves handing work off to a team that operates in Jira, this integration can create the Jira issue automatically and notify you when it's done

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.



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. Only users with Administer permission for the Track can access this page.


Step 2 - Enable the Jira integration

The Integrations panel will show which integrations are available.
Click Enable next to Jira to begin.


Step 3 - Connecting your Jira account

Clicking Enable will open the Jira authentication pop up. Click to Accept the required permissions and to authenticate via OAuth.

Why these permissions are requested:
The integration uses OAuth to connect securely to your Jira account. It will request permission to read and write to your Jira projects. This is needed so it can create issues and receive status updates on your users behalf via webhooks.



Step 4 - Choosing a Jira instance

Once authenticated, you can click to Configure the Jira integration.

  1. Select the Jira site that you want to integrate with your Track in IO.
  2. After selecting a Jira site, you can choose a Jira Project (Where the issue will be created) and Issue Type (Which issue type will be created)


Step 5 - Configuring workflows

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 (IO Track → Jira).

See Step 8 if you want to receive Jira issues in ISMS.online (Jira → Track).


Step 6 - IO Track → Jira workflow

Use the first workflow if work that originated in a Track needs to be handed off to Jira. Toggle it on to reveal the configuration fields.

  • Escalate when Track Item reaches→ Choose the Track Item status that will trigger the creation of a new Jira issue. 
  • When Jira status reaches→ Choose a Jira issue status, this will be the trigger for the update back to IO. 
  • Update Track Item to→ Choose the status the Track Item will be moved to when the Jira update is triggered.


In the example shown below, when a Track Item reaches the 'Assessment' status, a new Incident issue is created in the Incident Resolution project in Jira. When that Jira issue reaches 'Done', the Track Item is automatically updated to 'Resolved' in IO.


Step 7 - Jira → IO Track workflow

Use the second workflow if work that originated in Jira needs to be handed off to a Track. Toggle it on to reveal the configuration fields.

  • Escalate when Jira Issue reaches→ Choose the Jira Issue status that will trigger the creation of a new Track Item. 
  • When Track Item status reaches→ Choose a Track Item status, this will be the trigger for the update back to Jira. 
  • Update Jira Issue to→ Choose the status the Jira Issue will be moved to when the Track Item update is triggered.


In the example shown below, when an Incident issue from the Incident Resolution project in Jira reaches the 'Escalate' status, a new Track Item is created in IO. When that Track Item reaches 'Resolved', the Jira Issue is automatically updated to 'Done'.



Final Step

Integration configuration saves as you make changes, once you are done you can leave the page and the integration is 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?Click Configure to see 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. Green means the workflow is currently enabled.
How do I disconnect my integration completely?In the integrations panel, click Configure, then Click Disconnect.
I enabled a workflow 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:


  • Any Subtask issue type is not selected
  • The right IO/Jira status is being used to trigger the workflow. 
  • You have permission to create/update Issues in your chosen Jira project


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