We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
The Zendesk API Documentation for Bulk Delete Tickets specifies a JobStatus is returned.
The problem is that the method signature in the client does not match:
zendesk-java-client/src/main/java/org/zendesk/client/v2/Zendesk.java
Lines 440 to 443 in e609033
Describe the solution you'd like
The method should return a JobStatus so that the caller can follow along with how the job progresses:
public JobStatus deleteTickets(long id, long... ids) { complete(submit(req("DELETE", tmpl("/tickets/destroy_many.json{?ids}").set("ids", idArray(id, ids))), handleJobStatus())); }
Describe alternatives you've considered
Delete tickets 1 by 1. Not an option as we are trying to limit the number of questions we submit.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Agreed, that would be a nice enhancement, pull request welcome!
Sorry, something went wrong.
Created a pull request for it. :)
No branches or pull requests
Is your feature request related to a problem? Please describe.
The Zendesk API Documentation for Bulk Delete Tickets specifies a JobStatus is returned.
The problem is that the method signature in the client does not match:
zendesk-java-client/src/main/java/org/zendesk/client/v2/Zendesk.java
Lines 440 to 443 in e609033
Describe the solution you'd like
The method should return a JobStatus so that the caller can follow along with how the job progresses:
Describe alternatives you've considered
Delete tickets 1 by 1. Not an option as we are trying to limit the number of questions we submit.
Additional context
N/A
The text was updated successfully, but these errors were encountered: