Skip to content

Multi-Jira setup

Sophos Cloud Optix can be configured to send alerts from any cloud environment to a different Jira instance or project. To upgrade, in Jira Integration, click Upgrade to Multi-Jira.

After your account is upgraded, you can create additional Jira integrations in Sophos Cloud Optix. Each integration is linked to an individual Jira instance. You can then assign your cloud environments to different Jira instances.

You can only link a cloud environment to one Jira instance. You can link a Jira instance to more than one cloud environment.

You can assign priorities to Jira instances in Sophos Cloud Optix. Priorities can be any integer. The priority set in the integration must match the priority set in the Jira instance.

Upgrading to multiple Jira instances

If you've already set up a Jira integration, the upgrade sets the priority of that Jira instance to 1. During the upgrade, all your existing cloud environments are linked to this Jira instance. You can migrate them to other Jira instances after the upgrade. See Migrating a cloud environment to another Jira instance.

If you didn't have an existing Jira integration when you upgraded, you need to add a Jira instance first, then link cloud environments.

When you've upgraded and set up more than one Jira integration, new environments you add to Sophos Cloud Optix aren't linked to Jira automatically. You need to link a new cloud environment to a Jira instance manually. If a cloud environment isn't linked to a Jira instance you receive an alert.

You can also create a new Jira integration without any cloud environments, and link them later.

After upgrading to Multi-Jira, you can't revert to single Jira.

Adding a Jira instance

To add an additional Jira integration to your Sophos Cloud Optix account, do as follows:

  1. Click Integrations.
  2. Click Jira, then click Add Jira.
  3. If you click Enable, the integration is turned on when you Save the configuration.
  4. Enter a Priority for the Jira instance.

    You can't use a priority that's already used.

  5. Enter your Jira URL.

  6. Enter the username and API token needed to connect to it.
  7. Enter the project key for the Jira project where you want the tickets to be created.
  8. In Environments, choose from the list of Available Environments, then click the arrow icon to move one or more into the Selected Environments list.

    The environments you select are linked to the Jira integration you're creating when you Save the configuration.

    If there are no environments in Available Environments, all your environments are already linked to another Jira instance. You must unlink them first.

  9. In Alert Levels:

    1. Select which Sophos Cloud Optix alerts create Jira tickets.
    2. Optionally, change the Jira priority set for each alert level in Sophos Cloud Optix.

      You must set the priority to the same priority as the Jira instance you're linking to. If it isn't, you can change the priority in Jira. You can use Test configuration to make sure this is correct.

  10. Select Automatic to create Jira tickets automatically from alerts.

    If you don't select this, the alert in Sophos Cloud Optix includes an option to create a Jira ticket manually.

  11. In Alert Post By, choose how Jira updates tickets.

    • Consolidated: Updates the existing Jira ticket if another resource is affected by the same alert, or if the status changes (as in the Sophos Cloud Optix alerts page). This is the default.
    • Affected Resources: Creates a parent Jira ticket containing only the title of the alert. Then creates a separate Jira sub-task for each resource affected by the alert, puts the alert details in it, and links it to the parent.
  12. Click Mark as close to close the tickets in the Jira instance linked to the cloud environment you're moving to this new Jira instance.

    If you don't select Mark as close the status of the tickets isn't changed.

  13. Enter a Close transition name to use in Jira tickets as they're closed.

  14. Select Add Compliance tags as labels to add policy tags as labels in Jira tickets.
  15. We recommend that you click Test configuration before saving your changes.
  16. Click Save.

The new Jira integration is created. All tickets in the original Jira instance are moved to the new instance. The following comment is added to the tickets in the original Jira instance:

Ticket is migrated to Jira <Jira URL> and project name <Project Name>

The tickets from the original Jira instance are copied into the destination one.

Managing Multi-Jira

After adding more Jira instances to your Sophos Cloud Optix account, your Jira Integration page changes.

When you click Integrations > Jira, you now see a list of the Jira instances added to your Sophos Cloud Optix account.

Click a Jira instance to see it, and change its settings.

You can click Add Jira to add a new instance.

Migrating a cloud environment to another Jira instance

To migrate a cloud environment to another Jira instance, you must unlink it from its current one, then link it to its new Jira instance.

While a migration is running, you can't create tickets manually for that cloud environment. Migration takes time, so we recommend you do it during a quiet period.

You can check the progress of a migration in the Sophos Cloud Optix audit log. Entries are made for the start and finish of a migration.

To unlink a cloud environment from its current Jira instance, do as follows.

  1. Click Integrations > Jira.
  2. Click the Jira instance with the cloud environment you're migrating.
  3. In Environments, select the cloud environment in Selected Environments, then click the arrow icon to move it to Available Environments.
  4. Click Save.

You can now link the cloud environment to a new Jira instance, or migrate it to an existing one.

Do as follows:

  1. Click Integrations > Jira.
  2. Click Add Jira for a new instance, or select an existing Jira instance from the list.
  3. Fill in the fields. See Adding a Jira instance.
  4. In Environments, select the cloud environment in Available Environments, then click the arrow icon to move it to Selected Environments.
  5. Complete the rest of the form.
  6. Click Save.

When migration finishes, the following comment is added to the tickets in the original Jira instance:

Ticket is migrated to Jira <Jira URL> and project name <Project Name>

The tickets from the original Jira instance are copied into the destination one.