Skip to main content
New Idea

Support for filtering and updated_since in /timeentries api endpoint

  • March 14, 2022
  • 1 reply
  • 47 views
hemenkapadia
Apprentice
Forum|alt.badge.img

Hi,

The current implementation of the /timeentries api does not have a good way to limit the entries to support a delta extract pattern (i.e. new entries added or updated since a last extract time)

The /tickets api does have these capabilities using the `updated_since` filter/feature.

 

Request - Enhance /timeentries endpoint to support the updated_since feature like the /tickets api. If this is not possible then support the filters order_by and order_type like the /tickets api; and ensure you support all datetime type fields in timeentries for the order_by filter.

 

This is critical for the indepth data analysis and dashboard we need to prepare.

Regards,

Hemen

 

 

 

    1 reply

    A
    Community Debut
    • Arno
    • Community Debut
    • April 8, 2024

    I second this request.

    We do face the same issue while fetching time entries for billing purposes:

    we can filter by executed_after, but that filter is for the timestamp the actual work took place. When fetching entries for billing, we would like to make use of updated_since or updated_after similar to the filter in tickets, as we can then fetch all time entries created or changed since the last billing cycle.

    With the current available filter, we always have to fetch a large amount of entires and match them against our own database-driven way of selecting the relevant ones not yet billed.

    Please introcuct updated_since, it’s an easy change and helpful for so many use cases and would also be consistent with other API calls for other entries. Thanks!

    Terms of UseAccessibility statement