List of deleted ticket numbers

Martin Pilkington's Avatar

Martin Pilkington

12 Feb, 2009 10:52 PM

Every time I perform a full update in Lighthouse Keeper I have to download every single ticket from every project in every account just so I can check if a ticket has been deleted on Lighthouse. For my account this currently means 487 tickets need to be downloaded, which on the auto update setting is every 30 minutes. This is 17 requests at the best of times, assuming they're all in one project and none have been updated. During my tests I had 8 tickets needing updating so that's 25 requests, though we can probably push that closer to 30 requests as I have 7 projects

What would make things much easier and more efficient is a list of deleted ticket numbers. Even if is only storing them for 30 days, though deleting tickets isn't that commonplace an activity in my experience, it would be useful. It would be even better if it could be requested per account rather than per project as it would mean even fewer requests, 1 vs 7 in my case, though obviously due to private/public projects it may be easier to keep these per project.

I could then reduce my update requests to 2 requests per project most of the time. 1 to get the tickets updated since the last day I checked for tickets (this could increase if there's more than 30 tickets to download) and 1 to check for deleted tickets. In this case I'd end up with 22 requests returning little data in my above case, 14 when there are no updated tickets (vs the 20+ I have to make when there are no updated tickets at the moment).

I've been looking around for ways to help reduce the number of requests as this obviously helps me in the time it takes to download and you in the number of requests you have to serve up. Any ways you can come up with to reduce the number of requests to actually get the data via the API, I'm more than happy to recode parts of LHK for to take advantage of.

  1. 1 Posted by Rick on 14 Mar, 2009 02:28 PM

    Rick's Avatar

    Hmm, what if you could just do a query on a range of tickets? #1 [#23](/discussions/api-developers/23 "Discussion #23") [#15](/discussions/api-developers/15 "Discussion #15") [#235](/discussions/api-developers/235 "Discussion #235") could just return whatever tickets still exist.

    Also, are you doing anything with http conditional GET? Attempting to update an individual ticket could return a 304 NOT MODIFIED which would save LH from rendering the XML.

  2. brandi closed this discussion on 29 Jun, 2012 10:10 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac