API: search tickets and time entries by date-range and customer-ID
Currently if we want to use the APIs to pull certain tickets or time entries for a particular client and/or a particular timeframe, we have to pull ALL THE TICKETS in our Atera account (which takes a long time, and generates a lot of traffic to Atera's servers).
Can you please add additional criterias to avoid all this extra traffic and make the API calls faster?
Time Entries and Tickets search:
* Before date-time
* After date-time
* Customer ID
* String in comments (all words, or any words).
Thank you!
-
Jim Rossi commented
i created another workaround for this. with the new feature to allow for additional ticket statuses, i added an archived status. then i created a script to change the status of all tickets where the TicketResolvedDate is 45 days ago to my new Archived status. now i can run the api calls for the closed ticket in much less time. i hate that it is a work around, but it works.
anyone with this issue and less tickets might be able to do this with the new time based automation rules. they just won't work on existing tickets, but it may work on newly created tickets. -
Jim Rossi commented
my current work around is terrible, but i pull down all the open tickets in one script and all the pending, resolved, and closed in another. i store the data in json files and then read in those files as needed in my customer portal. it is not the best way, but until they let us pull only records updated since X, that is what i have to do. my closed tickets are delayed up to 30 minutes.
-
Barry Hayward commented
Any advice on how to do this currently?
I agree having the Time Entries and Tickets search: as per desciption would also be beneficial.