Recent searches


No recent searches

How can I share feedback for the Sandbox Deploy Automations closed beta?



image avatar

David Hall

Zendesk Product Manager

Posted Sep 08, 2023

How to give feedback?

This Community forum is the best place to share your feedback, so other customers can join in the conversation and add their own perspectives.

When you have feedback to give, have a look at the existing posts in this forum and see if you can benefit or contribute to the feedback that others are discussing. If no existing posts seem relevant, then feel free to create a new post. 

Suggested guidelines for giving feedback

We value your feedback, no matter what it is. We encourage you to tell us what you like, dislike, and where you could see improvements. We'd like to see a healthy forum for discussion, but we can't do that without just a little bit of effort from everyone. 

Here are a few pointers that will really help us understand your feedback and work with you to make the sandbox experience even better:

  • When you see something you dislike or see something you'd like improved, write it down and think about it for a little while
  • Try to be as clear as possible in your feedback; explain why you like/dislike something, and how it could be improved. If you can do screenshots easily, we'd love to see them
  • Be patient when waiting for responses from Zendesk
  • Don't use sarcasm, be rude to other customers or staff, and don't use strong language. We will moderate forum posts where we think reasonable

Ultimately, we want the feedback forums to be a place where any customer can come and give feedback.

Reporting bugs

As this feature is in beta, the best way to report a bug is to do so here in this forum, rather than raising a ticket. This is especially helpful if you're reporting a minor bug or a bug that is not directly impacting your customers.  As this is a beta, the response times may be longer than they typically would be going through the normal support channels.


1

7

7 comments

When deploying from the sandbox to production, the tool appears to use the naming descriptions for dependencies. Would it be possible to understand how the tool matches configurations, is it through naming descriptions?

I only ask, as we deploy from sandboxes to production on a regular basis and sometimes the naming conventions may not always be the same. They may be updated in production at a later date.

The deployment tool within the admin center, when a dependency issue is found, and you have the option to create the dependency in production, it would also be helpful to be able to match to an existing one, maybe by using the name or ID.

0


image avatar

David Hall

Zendesk Product Manager

0


I'm trying to deploy a few automations but get the error This configuration has dependencies that aren’t supported, so it can’t be deployed.” with no indication what dependency is causing the error. There is also no link to the automation in production to quickly check.

The fields exist in both so my assumption here is that the dynamic content is missing (can't search DC, so.), could this cause the error?

The dependencies are definitely a headache creator, after changing three automations in sandbox I now have to go into production and change these three again.

0


image avatar

David Hall

Zendesk Product Manager

Hi Joey, thanks for the feedback.  You are probably on the right track about dynamic content being a blocker, as DC is not currently supported in deployments.  I see you've signed up for a face-to-face session with us, looking forward to digging into this in more detail with you.

0


image avatar

Jamie Noell

Zendesk Luminary

The Deployment feature is a good first step.  Here are some suggestions:
1.  Sometimes the Deployment screen just shows order updates because there is a new trigger which has impacted the order.  I see that when I deploy the new trigger, Zendesk is handling the trigger order, so why are the ‘order only’ triggers showing as needing to be deployed?

2.  If you want to show them, could you just designate “order only” (meaning no configuration / conditions or actions change)?

3.  Salto has a similar deployment product, and I liked how they treat email conditions or actions - just looking at the non-email domain part of the email and doing a match between sandbox and prod (e.g., look at support@ of techsupport@abc.com and match techsupport@abc-sandbox.zendesk.com).  As it stands today, we have to update triggers after deploying to set any received@ criteria.

4.  Could you please add a “completed” or “deployed” status to the Deployment screen? With multiple admins, this would help us in monitoring what's been deployed from sandbox.  

5.  Could you please add an “ignore” option to the Deployment screen?  With multiple admins, this would help us differentiate between triggers we purposefully do not migrate.

 

We look forward to / hope to see other deployment options between sandbox and prod and if we are really dreaming, a comparison, like Salto, where it compares the 2 environments and identifies what's out of alignment.  :)

 

 

0


image avatar

David Hall

Zendesk Product Manager

Hi Jamie, thanks so much for the detailed feedback. We'll take that on board as we continue to improve the deployment experience.

0


Hey David Hall 

We have noticed some new features in the deployment functionality, mainly that webhooks are now being flagged as dependencies which is great.

Have there been any other added functionality that we might not know about?

(I just noticed this post is about automations, my question is about triggers)

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post