Settings and activity
37 results found
-
9 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Jim Rossi
supported this idea
·
-
7 votesJim Rossi
supported this idea
·
-
4 votesJim Rossi
supported this idea
·
-
5 votesJim Rossi
supported this idea
·
-
1 voteJim Rossi
shared this idea
·
-
6 votesJim Rossi
supported this idea
·
-
13 votes
An error occurred while saving the comment An error occurred while saving the comment 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.
Jim Rossi
supported this idea
·
-
2 votesJim Rossi
shared this idea
·
-
3 votesJim Rossi
supported this idea
·
-
2 votesJim Rossi
supported this idea
·
-
8 votesJim Rossi
supported this idea
·
An error occurred while saving the comment Jim Rossi
commented
also important to lock down the api key to access only a single client.
-
3 votesJim Rossi
supported this idea
·
-
7 votesJim Rossi
supported this idea
·
-
18 votesJim Rossi
supported this idea
·
-
36 votesJim Rossi
supported this idea
·
-
61 votesJim Rossi
supported this idea
·
-
5 votesJim Rossi
supported this idea
·
-
17 votesJim Rossi
supported this idea
·
-
20 votesJim Rossi
supported this idea
·
-
48 votesJim Rossi
supported this idea
·
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.