165

Replicating your config on your sandbox

It would be great to be able to replicate your environment in your sandbox. There is an export facility in the prod box, but there is no Import facility. Having a sandbox that doesn't mirror your prod box is pretty much useless, and having to redo all the config manually on the sandbox is extremely time consuming!!!

This is the first thing that any customer with a sandbox will be asking for.... and I'm probably not the first one!

66 comments

  • 0

    Agreed, I would love to be able to port over my widgets and triggers into the sandbox.

  • 3

    Also in the other direction, promote from Sandbox to Production - this would be a logical deployment pattern. Develop & test in the Sandbox, deploy into Production.

  • 0

    I'd like to understand if there is any ability for us to develop pre-production staging config, as well as add content to Forums, People, etc, that would then allow us to migrate and deploy into production when ready.  With the new Forums in our Sandbox, even an API would be an acceptable workaround so that when they go live in production, we can quickly populate content, etc.

  • 2

    I vote for the ability to promote from Sandbox to Production. I've stopped using Sandbox simply because of the added effort and duplication errors migrating configs to production.

     

    christopher

  • 0

    I agree. I'm posting several topics into forums and it's not going to be much fun to repeat the process in the live environment.

  • 0

    I strongly support the need for functionality that would allow selective migration of Forum articles from Sandbox to Production. Cutting and pasting isn't very efficient. Or am I missing something in my interpretation of this functionality?

    • Geoff
  • -1

    Would be great as the complexity of mirroring is difficult.

  • 0

    Perhaps when you run the operation to import changes from your sandbox, there can be a selection prompt asking what and how you want it imported.  Imagine seeing a checkbox for Forums, People, Views, Macros, etc.  That way you can pick and choose what you want and what you don't to avoid problems.  Also, a drop-down next to each item that lets you select only new entries, mirror it exactly, etc.  That way you have as much control as almost anyone would possibly need.

  • 0

    Assuming identity of an Agent or User has been one of the most useful features for us when developing content and fields. Assuming and exporting the identity of the Sandbox or the Main Site would be equally useful. We need a Sandbox promotion or export to live feature.

  • 0

    I've got the same request. We always have staging environments at work and we'd very much like one for Zendesk too. I'm sure that Zendesk itself has a staging environment for it's own teams!

    The sandbox feature is useless to us without a way of copying our current production environment. Sure, we could manually recreate our business rules but it's too much work.

  • 1

    I'm pleased to advise that Coherence Design - (http://www.coherencedesign.co.uk/zendesk-implementation/) have now developed a capability to export and import all configuration elements (triggers, automation, targets, custom fields, widgets, macro, and views). This will serve as the basis for a commercial web service and widget UI to enable staging promotion to a production environment and many other scenarios, including version control.

    This will be launched shortly, but please contact me (graham.robson@coherencedesign.co.uk) if you want to get involved at a beta project level.

  • 0

    As there is is no releasing process for contents (e.g. an articles is written but not reviewed and needs to be released by a reviewer) a sandbox with all contents and the possibility to stage the sandbox changes would be very helpful.

  • -1

    Michael has opened a feature request for deploying from Sandbox to Production... may pay to make some of these comments here... https://support.zendesk.com/entries/251763-deploy-from-sandbox-to-production

    I think both would be valuable.

     

  • 0

    My +1.

  • 0

    It would be extremely valuable to be able to copy over all of our triggers and then also be able to one click to enable the new trigger that has been tested to save time going to and from testing. 

  • 0

    +1

  • 0

    +1

  • 0

    +1

  • 0

    +1

  • 0

    Where is the ZenDesk staff on this one?  I cannot believe I didn't realize this need before seeing this request. Absolutely agree.  Sandbox isn't very helpful at the moment, but it would be priceless with a few updates.

  • 0

    Can I assume ZenDesk is working on this?  Over two years ago, and there has been NO reply by a staff member.

  • 1

    Hey guys,

    While I'd love to also see this feature (and perhaps even the ability to specify exactly what to sync back down to the parent) it's unfortunately not going to happen in the near future.

    At the moment sandboxes are just another Zendesk account which is tied to your own account. We move a few things over such as settings and users, but we do that at the point of the account's creation. We have no mechanism to then sync anything after this point.

    This project would essentially involve us completely changing sandboxes, and is thus a substantial engineering effort. Unfortunately there's likely no room between everything else on the roadmap for this year.

    When we revisit this area, we'll certainly keep everyone in the loop about any plans and beta.

  • 1

    In case anyone missed this in the thread trail, Coherence Design have a full commercial extension capability called Configuration Manager that allows you to extract builds of custom fields, triggers, views, macros, reports, automations, groups, and widgets. These can then be deployed to another Zendesk, typically used between prime and sandbox instances.

    To be clear this isn't syncing, which is a substantial undertaking, rather it's a set of tools that admins can use to enable portability of configurations.

    If your interested in exploring, contact info@coherencedesign.co.uk.

    Graham

  • 0

    Okay this was killed about 10 months ago but really should be revisited.  We are in the midst of transitioning all of our support channels to Zendesk and our understanding of the Sandbox was we could test before deployment.   I spent lots of time developing triggers and automations when agents started entering phone conversations as tickets and then before transitioning our next channel e-mail I created a Sandbox.  Then we started getting a flood of notification e-mails that we had previously customized, we also noticed not all groups were carried over.  This meant lots of time recreating work that had already been done.

    I understand not being able to dynamically add content from the other account without a redesign, but at creation couldn't the old account be basically cloned in terms of triggers etc. This would at least allow testing new things, and then later if a redesign is added to the roadmap have it able to go the other way as well.  Think it is about time for an update on this one.

  • 0

    ++++++++1 to this one

  • 0

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++1

  • 0

    We're working on updating our triggers and such and not having this feature makes that pretty aggravating. I'm not holding my breath, but this would be really nice to have.

  • 0

    I agree that it would REALLY be helpful to be able to export triggers etc. from production to Sandbox. As it is today, it would take me a week or so just to set up the environment in Sandbox, and then I still don´t have any tickets to play with.. 

  • 1

    To have a choice:   Clone current settings into a new Sandbox, or Create an Empty Sandbox would be just fantastic.

     

  • 1

    Hey,

    Have a look on our ZenDesk migration tool :  https://github.com/fourmation/ZenDeskMigration :)

Please sign in to leave a comment.