Bug Report: timelog startDate and endDate timestamp not optional?

Chris Baker

Hi, I've been working on a script that pull my team's hours by person each week at a time.

I've been running into an issue where timelogs on edge dates don't show up as expected.

For example, when I query for May 5th - May 11th, the test timelog for May 11th isn't being returned.

Here's the API parameters in use:
{me=true, trackedDate={start=2025-05-05, end=2025-05-11}}

Here's the output (8hrs on 2025-05-11 is missing):

However, when I specify timestamps, which the documentation states are optional, the correct timelog data is returned.

Here's the API parameters with timestamps:
{me=true, trackedDate={end=2025-05-11T23:59:59, start=2025-05-05T00:00:00}}

And here's the output:

Are others noticing this, too? Is this a widespread issue in the documentation/API? Should I always be treating date range timestamps as required?

Find more posts tagged with

Comments

ChoongSeng Chen

@Chris Baker

Have you tried out specifying the timezone in your datetime parameter?

Chris Baker

Thanks for the idea, @ChoongSeng Chen!

The documentation for `GET /timelogs` doesn't indicate that a timezone can be specific in the `trackedDate.start` or `trackedDate.end` parameters.

Can you explain how specifying a timezone might solve the issue, though? A timestamp is optional, the documentation says, so I'd expect the API to return the correct timelogs even if the concept of time were omitted from the request parameters.