Round robin ticket assignment | Community
Skip to main content

Round robin ticket assignment

  • December 10, 2013
  • 111 replies
  • 0 views

Show first post

111 replies

Looks like changes to Zendesk's platform makes this workaround unusable. Looking for insight to resolve this. Christopher

Here's the output of running each process:

testGetFormColumn

Method Range.getComment is deprecated.Collapse*File: *zendeskMakeAssignments *Line: *313The method has been marked as deprecated which means that the feature should be avoided and may be removed in the future. Consider using an alternative solution.

with a similar message after running makeAssignments

Cannot find method getRange(number,number,number,(class)). (line 285, file "zendeskMakeAssignments")

seekOpenTickets

Request failed for https://undefined.zendesk.com/api/v2/search.json?query=type:ticket%20status:new%20assignee:none returned code 404. Truncated server response: { "error": { "title": "No help desk at undefined.zendesk.com", "message": "There is no help desk configured at this address. This means t... (use muteHttpExceptions option to examine full response) (line 159, file "zendeskMakeAssignments")

a similar message for getOpenTickets

Request failed for https://undefined.zendesk.com/api/v2/tickets/recent.json returned code 404. Truncated server response: { "error": { "title": "No help desk at undefined.zendesk.com", "message": "There is no help desk configured at this address. This means t... (use muteHttpExceptions option to examine full response) (line 137, file "zendeskMakeAssignments"

 


  • Author
  • January 28, 2015

Hi all,

@Ravi, Sorry your having trouble with this! Unfortunately, I am unable to view the screenshots you have provided. Would you mind sharing them with me here: mike@bettercloud.com

@Christopher, Interesting, the script is still working on our end. Would you mind sharing your script with me so I can take a look at it? Please share with: mike@bettercloud.com

Thanks!

Mike

 


  • January 28, 2015

I tried too many times but dropped the ball now. You can ignore my request on this.


@Michael will do


  • Author
  • January 28, 2015

@Ravi -- sorry to hear that! If you decide to give it another try feel free to reach out.


  • February 12, 2015

Hi ZD Community -

This may be common knowledge for the more technical, but be sure to EXCLUDE the [ ] when you enter your information in to rows 10, 23-25 in the script editor.  

Hope this saves you some time troubleshooting


Jennifer16
  • February 12, 2015

Ryan, thanks for sharing the troubleshooting tip!


  • March 11, 2015

Hi all,

We have also been using this application for a few months, and it was a life changer.

I am however encountering an issue.

I know that this application's template was created on the old version of Google Sheets, which works fine for me.

The issue is, if I create an application from scratch using the newest version of Google Sheet, the application does not run.

I receive the error message

"Line 63 - Your spreadsheet has reached the maximum of 5000 characters per cell".

Line 63 in the script is the following:  logSheet.insertRowBefore(2)

I cannot figure out what causes this error.

Has anyone run into a similar issue?

Thanks


  • March 31, 2015

I am also receiving the error below when trying to run the MakeAssignments trigger

Request failed for https://raceitsupport.zendesk.com/api/v2/search.json?query=type:ticket%20status:new%20assignee:none returned code 422. Truncated server response: {"error":"invalid","description":"Invalid search"} (use muteHttpExceptions option to examine full response) (line 160, file "zendeskMakeAssignments")

 

I didn't make any changes to the code so I'm not entirely sure what's going on... @Gareth or @Michael what was the solution for this?


  • May 7, 2015

 

Here i am receiving the error

returned code 401. Truncated server response: {"error":"Couldn't authenticate you"

 

 


  • May 22, 2015

Hi all,

I'm doing some research on the problems Zendesk customers are trying to solve with this (or other) round robin processes. If you're interested in chatting with me about round robin or the general problem of agents cherry-picking tickets, drop me a line at eboyle@support.zendesk.com.

Thanks in advance!

Erin


  • November 18, 2015

Hi folks!

I'm trying to get this going, but I'm having trouble.

Looking at the Execution Transcript I can see that it's isolating out the right tickets, (the ones unowned ones with the tag).

But the script is consistently throwing this error:

Your input contains more than the maximum of 50000 characters in a single cell. (line 63, file "zendeskMakeAssignments")

Any insight is appreciated!

 


  • Author
  • November 23, 2015

Hey @Amanda,

Sorry for the delay in response! Please try commenting out (or completely deleting) line 32:

"debugSheet.getRange("A2").setValue(searchTickets);"

To comment it out, simply add "//" to the beginning of the line. It will look like this:

" // debugSheet.getRange("A2").setValue(searchTickets);"

Once you have done this, re-run the script and let me know the results.

Thanks!

Mike


  • November 24, 2015

@Michael,  Thank so much! That did in-fact allow the script to the ticket assignment; I think we're good! :D


  • Author
  • November 24, 2015

Awesome @Amanda! Happy to help.


  • December 8, 2015

Hoping someone could assist I am getting the below error and our calls are not being assigned to anyone

 

Bad request: https://fctsa.zendesk.com/api/v2/tickets/102497.json (line 193, file "zendeskMakeAssignments")


  • Author
  • December 8, 2015

Hey Nadia,

Google is experiencing some serious issues today which are almost definitely causing these failures:

https://status.cloud.google.com/incident/appengine/15025

 

Hope this helps. Sorry for any inconvenience.


  • December 8, 2015

Google apps is back up but the problem still persists.

Seems like the zendesk API might be acting up. I get the following header when trying to assign via curl:

X-Zendesk-API-Warn: Removed restricted keys ["{\"ticket\":{\"assignee_id\":0000000000}}"] from parameters according to whitelist

*note, I changed the actual assignee_id to all zeros.

The call I made was:

curl https://ttgithelp.zendesk.com/api/v2/tickets/00000.json -H "Content-type=application/json" -d '{"ticket":{"assignee_id":0000000000}}' -v -u email@removed.com/token:tokenremovedforsecuritypurposes -X PUT

 

I am getting the same "removed restricted keys" warning header with any PUT /api/v2/tickets/{id}.json call.


  • Author
  • December 8, 2015

Thanks @Eric, I'm still experiencing issues as well. Wrote into Apps Script help forum and community. Hoping to hear back soon. I'm experiencing this issue with a number of scripts and APIs. Not entirely sure it's specific to Zendesk API, but definitely possible.


  • Author
  • December 9, 2015

Hey all,

Figured it out -- you will need to:

1) Head into your script (Tools > Script Editor)

2) Replace lines 182-190 with the following:

https://gist.github.com/anonymous/179b6b18b28afc2351d3

I've updated the template file attached to this post as well.

Let me know if you have any questions on this.

Mike

 


  • December 9, 2015

Hi Mike

 

You are a legend just made the changes on my end and round robin is working again.

 

Thank you for your help!!


  • Author
  • December 9, 2015

Awesome!! Happy to help


  • December 9, 2015

Michael, you've done it again. Thank you tremendously.  It's truly appreciated.

 

@communitymoderator - Not to underscore the work Michael has done for me and others in the Zendesk community, but can you please explain why we can't have this added as an application or out of the box functionality for Zendesk? 

 

Thank you! 


  • December 10, 2015

Michael, thank you for your help! The script works now. Could you please shed some light, what was the reason? Was something changed in ZenDesk API?


  • Author
  • January 4, 2016

Hey Alina,

Apologies for the delay. The script broke due to a change Google made on the Google Apps Script service. More specifically, they changed the way you configure the headers of an OAuth request.

For more info, take a look here: https://plus.google.com/u/0/+MichaelStone4/posts/2Qe7UbFnRZC

Hope this helps.

Mike