{"id":33,"date":"2012-06-20T10:31:25","date_gmt":"2012-06-20T09:31:25","guid":{"rendered":"http:\/\/tempdetheux.food.blog\/2012\/06\/20\/zendesk-change-the-default-priority-names\/"},"modified":"2019-07-19T17:02:05","modified_gmt":"2019-07-19T15:02:05","slug":"zendesk-change-the-default-priority-names","status":"publish","type":"post","link":"https:\/\/arnaud.detheux.org\/blog\/zendesk-change-the-default-priority-names\/","title":{"rendered":"Zendesk: change the default priority names"},"content":{"rendered":"
<\/div>

When we defined the Mondial Telecom<\/a> SLA, we decided to use our own priority names instead of the usual high & normal ones. Don\u2019t ask why \ud83d\ude42<\/p>\n

The Problem
\nThere is no way to edit the default Zendesk priority names. Which makes sense since you can simply create custom fields and disable the default ones. However the issue I had with that is firstly the way GoodData handles custom field metrics. With a system drop down menu, in GoodData<\/a> you have a neat report. Custom fields are supported but the way they are displayed in GoodData is less powerful.<\/p>\n

<\/figure>\n

The other issue is that we used our Zendesk for some time with the default priorities names. Changing suddenly in the middle of the process to custom drop down menus would have messed all that.<\/p>\n

The solution
\njQuery comes to help! With a tiny JS snippet (to enable via Manage> Extensions in your Zendesk) you can easily change the priority names in the ticket creation view and the tickets views. I skipped the macros & triggers for now. So now we have the best of both worlds: custom priority names & awesome metrics in GoodData reports.<\/p>\n

Please note that it\u2019s actually Skip Moore<\/a> from Zendesk who published the code to change the names in the ticket creation view on his GitHub account<\/a>.<\/p>\n

<\/figure>\n

The code<\/p>\n

\/* Original code from Skip Moore of Zendesk - https:\/\/github.com\/skipjac\/zendesk-widgets<\/a> *\/\n$j('#ticket_priority_id option[value=1]').text('G3');\n$j('#ticket_priority_id option[value=2]').text('G2');\n$j('#ticket_priority_id option[value=3]').text('G1');\n$j('#ticket_priority_id option[value=4]').text('G0');\n\/* Added this to display the correct priority name in the Views *\/\n\/* Update 16082012 - added the class to avoid breaking your CSS customization *\/\n$j('span.priority_normal').replaceWith('G2');\n$j('span.priority_low').replaceWith('G3');\n$j('span.priority_high').replaceWith('G1');\n$j('span.priority_urgent').replaceWith('G0');\n\/* Update 19082013 - added the changes to the \"view your existing request\" interface *\/\n$j(\"#widget_fixed.draggable div.side-box-content p:contains('Low')\").replaceWith('NEW NAME');\n$j(\"#widget_fixed.draggable div.side-box-content p:contains('Normal')\").replaceWith('NEW NAME');\n$j(\"#widget_fixed.draggable div.side-box-content p:contains('High')\").replaceWith('NEW NAME');\n$j(\"#widget_fixed.draggable div.side-box-content p:contains('Urgent')\").replaceWith('NEW NAME');<\/pre>\n
It\u2019s available here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
When we defined the Mondial Telecom SLA, we decided to use our own priority names instead of the usual high & normal ones. Don\u2019t ask why \ud83d\ude42 The Problem There is no way to edit the default Zendesk priority names. Which makes sense since you can simply create custom fields and disable the default ones. However…<\/p>\n
Read More  Read More<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","jetpack_post_was_ever_published":false},"categories":[7],"tags":[63,20,29,30,38,57],"class_list":["post-33","post","type-post","status-publish","format-standard","hentry","category-customer-experience","tag-archive","tag-customer-support","tag-gooddata","tag-hack","tag-javascript","tag-zendesk"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/posts\/33","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/comments?post=33"}],"version-history":[{"count":2,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/posts\/33\/revisions"}],"predecessor-version":[{"id":451,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/posts\/33\/revisions\/451"}],"wp:attachment":[{"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/media?parent=33"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/categories?post=33"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arnaud.detheux.org\/blog\/wp-json\/wp\/v2\/tags?post=33"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}