The API 3.0 Doc referenced in the first comment does not specify "status_id" as a valid parameter, rather, it states "status" should be used. Setting the GET parameter "status" to "completed" (as stated in the API Doc) will not return completed tickets, it returns "success" => 1.
Unfortunately, our dev team spent hours finding the correct helpdesk model/controller in the source to modify this prior to seeing this comment.
The API 3.0 Doc referenced in the first comment does not specify "status_id" as a valid parameter, rather, it states "status" should be used. Setting the GET parameter "status" to "completed" (as stated in the API Doc) will not return completed tickets, it returns "success" => 1.
Unfortunately, our dev team spent hours finding the correct helpdesk model/controller in the source to modify this prior to seeing this comment.
Yes, there are several undocumented options. We've adjusted the status option. The API Doc is updated. Please unzip attached archive to application/3.4.5/modules directory. When it is done you can use the following request in order to get active and completed tickets:
Yes, there are several undocumented options. We've adjusted the status option. The API Doc is updated. Please unzip attached archive to application/3.4.5/modules directory. When it is done you can use the following request in order to get active and completed tickets:
You can get all the tickets by using reports from left agents bar. Just click on Browse and select type-tickets
You can get all the tickets by using reports from left agents bar. Just click on Browse and select type-tickets
But with the API is this possible?
But with the API is this possible?
Replies have been locked on this page!