The Salto Jira adapter supports both Jira Cloud and Jira Data Center, enabling you to:
Fetch and deploy key Jira configuration data, such as workflows, custom fields, and screens.
Copy configuration changes from your Jira Sandbox to production.
Compare different Jira instances to identify discrepancies.
Document configuration changes, such as workflow modifications.
Monitor specific changes of interest, such as updates to permission schemes.
See the Supported Jira Types page.
Connect your Jira Instance
Jira Cloud
To connect Jira Cloud to Salto:
Obtain an API Token from https://id.atlassian.com/manage-profile/security/api-tokens
Create a Salto environment and connect the Jira instance to it. See here how to create an environment in Salto.
In application credentials, provide:
Your Atlassian Base URL (e.g. https://acme.atlassian.net/)
The user email
The token you created in step 1
Jira Data Center
❗ To use Salto with Jira Data Center, install the Salto Jira Addon in your instance.
To connect the Jira Data Center to Salto:
Install the Salto Configuration Manager for Jira add-on in your relevant Jira DC instances. The add-on can be downloaded from the Atlassian marketplace. The add-on has been Data Center Approved by Atlassian.
If needed, configure your firewall to enable incoming connections from Salto's static IP addresses into your Jira instance.
Salto's IP addresses are available on this page.
Salto performs GET, PUT, POST, and DELETE requests for the following REST API groups:
/rest/salto/1.0/*
/rest/api/2/*
Create a Salto environment and connect the Jira Data Center instance by choosing "Jira Data Center" in the new application modal. See here how to create an environment in Salto.
In the next modal, enter the URL of the Jira DC instance and a valid username and password for that instance.
Advanced Configuration
Masking automation headers
By default, the Jira adapter retrieves all automation objects, including authorization headers, which may include a secret token. This helps seamless deployments of automations from one instance to another.
Salto can instead mask these tokens by replacing them with "<SECRET_TOKEN>" during fetches.
If the user deploys an automation with a masked authorization header, Salto will deploy this value instead of the correct token, and a user notification will be shown with the recommended Jira steps to enter the correct token
To enable this masking, go into the application settings and add the following to your configuration NACL:
masking = { automationHeaders = [ "Authorization", ] }
Jira duplicate names
If you get a message about duplicate Jira element names during fetch, such as "The following elements had duplicate names in Jira", visit the Salto ID collisions page to learn more about this issue, its impact, and possible solutions.
Known Limitations
Salto can not update a Project in free accounts
Salto can not create a project with a permissionScheme on free accounts
Workaround: comment out the permissionScheme value during deployments, and if needed, assign it to the project in the UI after the deployment
Deploying permission scheme does not work on free accounts
In Jira filters, Salto does not fetch or deploy subscriptions
Team Managed Projects and Boards are only partially fetched, and can not be deployed. This is due to Atlassian API limitations.
FAQ
Does Salto support Jira Service Management (JSM) enabled instances?
Yes - see Salto for JSM for more details
What impact does Salto have on my API limits?
| Concurrency | Total Requests |
What are the limits? |