Intrepid cuts Jira deployment time by 80% thanks to Salto

The engineering team building custom JSM applications at Intrepid faced significant challenges in managing configuration across multiple environments. They needed to accelerate the delivery of their bespoke JSM application while maintaining precise configuration synchronization across development, QA, UAT, and production environments. 

Manual processes were causing delays in project delivery and creating risks of configuration mismatches. After evaluating several options, including native Jira tools and competitor products, they chose Salto for its superior automation capabilities and intuitive change management features. By implementing Salto, they transformed their deployment process, significantly reducing manual efforts and ensuring consistency across environments.

Synchronizing Complex Multi-Instance Deployments

The team maintains four distinct Jira instances - Test, QA, UAT, and Production - each requiring identical configuration of workflows, fields, automations, and other customizations. 

Before Salto, managing these environments meant manually replicating configurations across each instance, a time-consuming and error-prone process. The folks at Intrepid needed a solution to package and deploy Jira configurations alongside their software deployments.

Their software development lifecycle involves developers working on local machines, with code automatically deploying to a cloud test environment, then QA testing, and finally, promotion to client test and production environments. Salto enabled them to mirror this process for Jira configurations, ensuring that all necessary configurations move seamlessly through each stage.

‍

‍

Ensuring Testing Reliability and Business Continuity

One critical challenge was maintaining testing reliability across instances. "If something exists in the QA site that the app depends on but isn't in the production instance, then a test could pass and fail in production," explained Alexander. Salto's ability to maintain consistent configurations across environments eliminated this risk, ensuring testing results accurately reflected production behavior.

‍

‍

Full Visibility and Controlled Rollbacks

Managing Jira configuration changes manually was not just time-consuming—it was risky. Without a straightforward way to track updates across environments, the team struggled with a high dependency on individual knowledge and a lack of visibility into past changes. With Salto, Intrepid’s team has complete visibility and control over their Jira configuration changes. Every update is tracked in a centralized history, ensuring nothing is lost. If a deployment causes issues, the team can instantly roll back to a previous state.