Product Feedback: Version Management (Environment Configurations) | The place for Zendesk users to come together and share
Skip to main content
Newcomer
Apr 8, 2026 9:15 AM UTC
Under review

Product Feedback: Version Management (Environment Configurations)

Related products:Admin center

Hello,

Following our evaluation of the Version Management feature (Environment Configurations) after its General Availability announcement, we would like to share some product feedback based on our sandbox testing. We hope these observations are useful as you continue to develop and refine the feature.

1. Snapshot language limitation & Production to Production environments restore restriction

We encountered two notable limitations around Snapshots:

Language dependency - The language of a Snapshot is tied to the account language at the time it is taken. When attempting to deploy from a Snapshot created in one language (for example Portuguese) to an environment set to a different language (to English), the deployment fails. There is no warning or indication of this at the point of taking the Snapshot or initiating the deployment, which makes troubleshooting unnecessarily difficult. We would suggest either making Snapshots language-agnostic, or surfacing a clear warning when a language mismatch is detected before deployment begins.

Production to Production restore restriction - For plans below Enterprise (which do not include a Sandbox), the ability to restore a Snapshot back to Production is directly tied to the existence of a Sandbox environment. This feels like a significant limitation, as it restricts access to a core recovery capability based on plan tier. We would welcome a review of this dependency, or at minimum clearer documentation around it.

2. Lack of detailed error information when deployments fail

When a deployment test fails, the feature currently notifies the user that the test was unsuccessful but does not provide specific details on why individual items failed. Similarly, Partially Deployed statuses indicate what was not pushed, but not the reason behind it.

For a feature that manages configuration changes across environments, actionable error information is essential. Without it, admins are left guessing, which increases the risk of repeated failures or incorrect workarounds. We would strongly encourage more granular and descriptive error outputs - ideally identifying the specific configuration item, the reason for failure, and a suggested resolution where possible.

3. No indication of who triggered a deployment

Currently, there is no visible record within the Version Management feature of which admin initiated a specific deployment. While the Audit Log may capture some changes, this is not surfaced directly within the Deployments view itself.

For accountability and governance purposes - particularly in environments with multiple admins - knowing who triggered a deployment is important. We would suggest adding an "Initiated by" field to each Deployment record, visible directly within the Version Management interface.

We believe Version Management has strong potential and are encouraged by the direction of this feature.

We hope this feedback helps prioritize improvements that would make it more robust and trustworthy for production usage.

4 replies

Contributor
Apr 8, 2026 12:53 PM UTC

I submitted this a couple of months ago. 

Without this, the ability to create snapshots is utterly useless for non-Enterprise accounts.

Translate
Shawna James
Community Manager
Jul 28, 2026 4:37 PM UTC
Updated idea statusFeedback submitted→Under review
Translate
Carl Joseph
Product Manager
Aug 6, 2026 11:10 PM UTC

Hi Aleksander. Apologies for the slow response on this one. 

Your feedback is incredibly useful and pretty much in-line with the improvements we would like to make with the product. Since your post we’ve released a number of updates that should help to clarify deployment failures and errors. We have more work planned around this to make things easier to diagnose as well, and that should be coming in H2 this year.

Production to Production deployments 

You can already deploy a snapshot that you took of a production instance back to that same production instance. In a way, use it as a roll-back feature. Deployment features only come with a sandbox (even if the deployment is within a single production instance). This is because we’d like to encourage more customers to make their changes within sandbox environments first before releasing them to production.

Who triggered a deployment

This is a really good insight, and definitely something we should add. We do track all the details about which user took each action (including deployment) so we should be able to add that to the table to display. Let me raise this with the team and see what we can do around this.

 

Thank you once again for the useful feedback. It’s much appreciated.

Translate
Contributor
Aug 7, 2026 11:49 AM UTC

​@Carl Joseph Please see 
https://community.zendesk.com/ideas/allow%2Drestoration%2Dof%2Dproduction%2Dsnapshot%2Dback%2Dto%2Dproduction%2Dfor%2Dnon%2Denterprise%2Dlicenses%2D1696 

It is not possible to deploy a Production snapshot back to Production unless you have an Enterprise license or have purchased a sandbox as an add-on. The cost we were quoted to add a sandbox to our Professional license was TWICE the cost of upgrading to Enterprise, for which we already have no business case. I continue to be forced to make all changes in my production environment, which I am incredibly reticent to do for obvious reasons. Which means that there are numerous potential ZD features that I might be interested in implementing but won’t even consider due to risk considerations. The ability to restore a snapshot would enormously de-risk things. The fact that I can snapshot my production environment but have no way to restore that snapshot is ridiculous.

Translate