mathieu.lepoutre

Hello 

With Exalate, you can have different tickets send different fields.

That is totally within it's Groovy Scripting Capability!

Exalate is a decentralized integration solution, where you can granuarly decide which data will be send over.

 

 

To have a ticket be reopened after closing, use Exalate.

It has groovy scripting capabilities, so all of that will become possible.

Exalate is a decentralized integration solution, where you can granuarly decide which data will be send over.

Hi 

Please have a look at Exalate, a decentralized integration solution that will help you with this.

You can granuarly decide which data you are sending from Zendesk out, and 1 of the issue trackers that we also support is Salesforce.

 

Thank you.

Kind regards,
Mathieu Lepoutre

Hi Lisa

 

This is probably a presentation bug. 

You can always have a look at Exalate, a decentralized integration solution that will give you full control over what gets sent. 

The nice things is that the node that sits on top of your instance is accessable outside of the ticket, this way this presentation bug is taken away.

 

Thanks

Hi Stephen

 

This is possible, yes. Take a look at Exalate, it would be perfect for a use-case like this. It is an integration solution wich a robust user interface where you can have scripting capabilities. You can add the latest comment to a field with it. I have been using it for quite a while and it instantly jumped in my thoughts reading this post. Hope to have helped you

Hi Nicholas

For tickets created via the custom bot, the first trigger fires, and for tickets created via email, the second trigger activates. This limitation might be due to your current setup.

Its my understanding that Exalate would be perfect for a use-case like this. It is an integration solution that works super fast in my opinion. II have been using it for quite a while and it instantly jumped in my thoughts reading this post. Hope to have helped you 

Hi Swati

 

When migrating from JC to JS, the process of migrating Zendesk data would require a separate approach, as Zendesk and JIRA are two different systems. Zendesk data migration typically involves exporting data from Zendesk and then importing it into the JIRA Server.

To achieve this, it's my understanding that using Exalate will be really beneficial for you.

Exalate is a powerful integration platform that not only allows you to synchronize data between different instances of JIRA but also supports integrations with other systems like Zendesk.

I have been using it for quite a while and it instantly jumped in my thoughts reading this post. It is an integration solution that works super fast in my opinion. Hope to have helped you and have a great day!

Hello

It's my understanding this is on Zendesk's roadmap and development plans.

In the meantime, if you require a solution for bi-directional sync between Zendesk and Salesforce and want more flexibility and control over the integration process, you might consider exploring  Exalate. It offers advanced synchronization capabilities and can help address data hygiene challenges by keeping your CRM and support systems in sync.

Hi

 

You can explore using workflow rules or automation features provided by zendesk. These rules can evaluate the change in the picklist field value and trigger an action, such as creating a new ticket. 

Seeing above reply that it is not supported natively. I would suggest having a look at Exalate, it is an integration solution and based on triggers you can make new tickets. Theres a full httpclient built into it which will get the change of Organizations.

Hope to have helped

Hi Nora

 

Are these tickets coming from a different instance?

There is an integration solution called Exalate that is fully decentralized where it is possible to selectively limit Attachments.