All Collections
Salto for Jira
Supported Jira Types
Supported Jira Types
Support avatar
Written by Support
Updated over a week ago

Salto supports Jira Cloud and Jira Data Center. Unless explicitly mentioned, all types below are supported for both versions.

Included Types

The JIRA adapter fetches and deploys the following element types by default:

  • Application Properties

  • Application Roles

  • Automations

  • Automation Labels

  • Boards (without swimlanes)

    • Salto fully supports fetching and deploying company-managed boards.
      Team-managed boards can only be partially fetched, and can't be deployed. This is due to Atlassian API limitations.

  • Configuration

    • Attachment Settings

    • Permission Settings

    • General Configuration

  • Dashboards

  • Dashboard Widgets

  • Fields

    • Field Contexts

  • Field Configurations

  • Fields Configuration Schemes

  • Filters

  • Groups

    • Fetched without the full user list

  • Issue Events

  • Issue Layouts (in early access)

  • Issue Link Type

  • Issue Type

  • Issue Type Schemes

  • Issue Type Screen Schemes

  • Notification Schemes

  • Permissions

  • Permission Schemes

  • Priorities

  • Priority Schemes (Jira DC)

  • Projects

    • Salto fully supports fetching and deploying company-managed projects.
      Team-managed projects can only be partially fetched, and can't be deployed. This is due to Atlassian API limitations.

  • Project Categories

  • Project Components

  • Project Roles

  • Project Types

  • Resolutions

  • Screens

  • Screen Schemes

  • Security Schemes

    • Including Security Levels

  • Statuses

  • Status Categories

  • Time Tracking Providers

  • Webhooks

  • Workflows

  • Workflow Schemes

Jira Addons

Salto fully supports fetching and deploying Jira Configuration of sites with Jira apps, plugins and addons installed.

In addition, Salto fetches and deploys configuration of the following apps:

ScriptRunner for Jira Cloud

Enable this by selecting "Enable ScriptRunner Support" when connecting to Jira

  • Behaviours (coming soon!)

  • Escalation Service

  • Listeners

  • Scheduled Jobs

  • Scripted Fields

  • Script Fragments

  • ScriptRunner settings

  • Workflow Scripts

ScriptRunner for Jira DC

Enable this by selecting "Enable ScriptRunner Support" when connecting to Jira

  • Workflow Scripts

Jira Service Management (JSM)

Enable this by selecting "Enable JSM Support" when connecting to Jira

  • JSM Projects, including

    • Calendars

    • Request Types

      • Issue View

      • Request Form

    • Forms

    • Portal Groups

    • Portal Settings

    • Queues

    • SLAs

    • Customer Permissions

  • Asset Object Schemas (JSM Premium / "Insight")

Enabling add-ons in existing Jira environments

In existing Jira Salto environments, to fetch configuration of Jira Addons such as ScriptRunner or JSM, add the correct addon to the "fetch" section of your environment's Salto Configuration File.

Here's an example which enables both JSM and ScriptRunner:

jira {
  fetch = {
    enableScriptRunnerAddon = true
    enableJSM = true
    
    include = ...

Excluding elements

You can edit the Salto Configuration File to exclude specific elements that you do not wish to fetch and manage with Salto. You can choose which types to exclude, and also which instances of these types. To do this, use the exclude list under the fetch section of the Salto Configuration File.

For example, this file excludes all automations which have "test" in their automation name:

jira {
  fetch = {
    include = [
      {
        type = ".*"
      },
    ]
    exclude = [
      {
        type = "Automation"
        criteria = {
          name = ".*test.*"
        }
      }
    ]
  }
}

You can also exclude specific Custom Fields according to their type. For example, this Salto configuration file excludes all multi picker fields from your fetches:

jira {
  fetch = {
    include = [
      {
        type = ".*"
      },
    ]
    exclude = [
      {
        type = "Field"
        criteria = {
          type = ".*multipicker"
        }
      }
    ]
  }
}
Did this answer your question?