Create a new project in Qordoba (see www.qordoba.com for more).
Download Qordoba's app from the Zendesk Marketplace
Copy and paste your token, Organization ID, and Project ID from your Qordoba project configuration into their respective fields in your Qordoba - Zendesk app setup.
Preparing for translation
Open the Qordoba app in Zendesk.
Select one or more articles, sections, or categories to be translated.
Click 'Send to Qordoba'
Once your translators finish working on a resource, the translation status for that resource in the Qordoba Zendesk app will be 'Completed'.
Select completed resources and click 'Publish Selected Translations'.
If successful, you will see the 'Translated' link for the resource activate.
For an end user to be able to navigate to an article in a foreign locale, you must ensure that the corresponding section and category are also published.
If you update the source article, you may re-upload it to Qordoba. Translators will only be prompted to translate new content.
You may use the 'Mark as Outdated' option in Guide Admin to help track which translations are outdated, but please note that you will have to manually mark the translations as outdated, and then manually remove the 'outdated' flag once updated translations are completed.
NO EDITING OF TRANSLATIONS SHOULD TAKE PLACE IN ZENDESK. All translation activity should take place on the Qordoba platform.
Create and link Clubhouse Stories from Zendesk tickets
Getting Your Zendesk Tickets onto your Clubhouse Stories board has never been easier! ### To Install * In Zendesk, click Install and enter your credentials to authenticate your Clubhouse account. * In Clubhouse, navigate to Settings > Integrations > Zendesk and switch the integration to ON Once the app is set up, it will be usable by everyone in your organization.
In order for this app to function properly, you'll need to ensure that the following steps are completed.
You'll need to fill in the app settings with values for the domain of your Zendesk app and optionally a list of custom ticket field IDs for fields that should be displayed in the split ticket form and finally (also optionally) a list of tags to be added to the new ticket. You will find full descriptions for all settings below.
Custom Field Ids — if you have custom fields in Zendesk that you use to add information to the ticket, these can be added to the split. Only 'Text' and 'Drop-down list' fields are supported currently. Field ids should be separated by commas.
Split Tags — if you would like one or more tags added to the new ticket, add the list here with each tag separated by a comma.
Show Group/Agent Assignee Field? — should the Group/Agent Assignee field appear for the child ticket. If checked, you can select the group or agent to which the ticket is assigned.
Enable Close Ticket Feature? — allows an administrator to suppress the Close Ticket feature of the plugin, if you do not want to allow your users to perform this functionality.
Add CCs to child ticket as default? — should the checkbox to add the CC list to the child ticket be on as the default?
Default Type value in Split — split tickets will default to use this as the Type. Valid values are 'question', 'incident', 'problem' & 'task', others will be ignored. An empty or invalid value will use the same Type as the original ticket.
Default Priority value in Split — split tickets will default to use this as the Priority. Valid values are 'low', 'normal', 'high' & 'urgent', others will be ignored. An empty or invalid value will use the same Priority as the original ticket.
Should the first comment of split tickets be public? — Should the checkbox to make the comment on the new ticket be on as the default? This is only valid if you have turned on “Allow first comment on tickets to be private” in the Tickets section of the Settings. Otherwise the comments are always public.
Questions and issues should be reported to our Zendesk.