Salto’s Jira adapter supports Jira Cloud and Jira Data Center, and allows you to:
Fetch and deploy common Jira configuration data, e.g., workflows, custom fields, screens.
Deploy major configuration changes from Jira Sandbox to your production environment.
Compare environments.
Document configuration changes such as workflow modifications.
Monitor specific changes of interest, e.g., permission schemes.
Supported Types
See the Supported Jira Types page.
Connect your Jira Instance
Jira Cloud
In order to connect Jira Cloud to Salto:
Obtain an API Token from https://id.atlassian.com/manage-profile/security/api-tokens
Add a Jira service to a Salto environment, by selecting the environment --> "Settings" --> "Add New Service".
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, start by installing the Salto Jira Addon in your instance.
In order to connect Jira Data Center to Salto:
Install the Salto Configuration Manager for Jira addon in your relevant Jira DC instances. The addon can be downloaded from the Atlassian marketplace.
If necessary, configure your firewall to enable incoming connections from Salto's static IP addresses into your Jira instance.
Add the Jira DC instance to Salto, by adding a new application to an environment and choosing "Jira Data Center" in the new application modal:
In the modal, enter the URL of the Jira DC instance, as well as a valid username and password for that instance.
The addon has been Data Center Approved by Atlassian.
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 right token
In order to enable this masking, go into the service settings and add the following to your configuration NACL:
Text
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 if it has a permissionScheme value on free accounts
Workaround: comment out the permissionScheme value, and if needed, assign it to the project in the UI after the deployment
Deploying permission scheme does not work on free accounts
The following types are not deployable:
Configuration
ApplicationRole
AttachmentSettings
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, we support Jira instances with JSM enabled.
Note that in some JSM enabled Jira instances, some objects can have duplicate names (such as custom fields or workflow statuses). While Salto will fetch these objects, we recommend users to rename these to unique names in order to correctly deploy relevant changes.
While we do fetch JSM projects, JSM specific types such as Queues and Request Types are not fetched today.
What impact does Salto have on my API limits?
| Concurrency | Total Requests |
What are the limits? |