Managing updates in Zendesk can be complex, especially when changes are made on the fly or directly in production. Teams often struggle to keep track of every modification, leading to misalignment, drift, and unexpected issues. Salto’s existing change log functionality solves that by providing visibility into all changes, whether they are planned deployments or ad-hoc updates. Salto's change log can help you effectively document and revert changes in your Zendesk environment, keeping your configurations in check and your team aligned.

Maintain complete change visibility in your Zendesk instance

Even with the best intentions, changes in Zendesk sometimes happen directly in production - sometimes to address urgent issues, many times because sandboxes have already drifted, so there’s little point to using them for testing. Documenting these changes, especially when they’re made on the fly or as hotfixes is challenging manual work. This makes understanding the true state of the configuration not a straightforward task.

Salto’s change log addresses this by capturing every modification—whether deployed through Salto or made directly in Zendesk. This ensures that no change slips through the cracks:‍

1. ‍Deployments: All changes pushed via Salto deployments are automatically recorded.‍
2. Fetches: Manual changes made directly in Zendesk are detected during Salto’s environment fetches. The frequency of these fetches is fully customizable—run them hourly, daily, or weekly based on your needs.

By continuously tracking changes, Salto empowers teams to keep their Zendesk environment transparent and under control.

Streamline change documentation for better collaboration

Salto’s change log isn’t just a record of what’s changed—it also serves as a documentation tool. Each change can be documented by editing its title and adding relevant details. For instance, you can link a change to a Jira ticket, making it easier for your team to understand the context behind modifications. This helps streamline collaboration, ensuring everyone is on the same page about what has been modified and why.

Quickly revert changes when issues arise

The change log also supports restoring specific configuration changes and is particularly useful for Zendesk admins. Here’s how it can be leveraged for efficient problem-solving:

1. Identify the change: Let’s say you discover that a new Zendesk form isn’t appearing correctly after a nightly fetch. With Salto’s change log, you can quickly search for the specific change that might have impacted it.
2. Selectively revert: Salto’s revert functionality allows you to recover specific changes without restoring the entire environment. In our example, you can selectively restore the missing form without affecting other recent updates.
3. Preview and validate: Before deployment, Salto validates the change, checking for dependencies and ensuring the restored configuration doesn’t break anything else in your Zendesk environment.
4. Deploy and document: Once validated, simply deploy the change, and Salto will create a new snapshot, ensuring your change log remains up-to-date.

This granular approach to reverting changes helps teams resolve issues quickly without disrupting other critical configurations.

Salto’s change log is a powerful tool for managing changes in Zendesk environments. It provides continuous visibility, robust documentation capabilities, and the ability to quickly revert specific configurations. By leveraging these features, teams can keep their Zendesk environment stable, collaborate effectively, and reduce the time spent troubleshooting unexpected changes. Sign up to try it or schedule your 1:1 session to see more.