Briefly describe (1-2 sentences) the Bug you’re experiencing:
Obtain the tasks that have been modified since a certain date-time. When filtering the gettasks by the project gid, it works fine. However, when doing so with the section gid, it seems that the modified_since parameter is not triggered and I obtain all tasks within the section regardless of their last modification date.
Steps to reproduce: get taks by section and modified_since parameters
Hi @anon77486349, sorry to hear that this is affecting you and that the workaround isn’t great due to the lack of pagination. The API team is actively working on this bug. I don’t have a firm date, but I would estimate it will be fixed in the next few weeks.
I talked with our API team and we think that there might be some confusion with how completed_since works.
The completed_since query param can be a bit confusing because it includes both completed and incomplete tasks. It should really be called something like incomplete_and_completed_since because using this query param will return tasks that are completed and incompleted since the specified date-time.
Let’s say you have a project with Section 1 (GID: 123)
Task 1 [COMPLETED - 06/14/2023]
Task 2 [INCOMPLETE]
Task 3 [COMPLETED - 06/14/2023]
Let’s say your request look like: /tasks?section=123&completed_since=2023-06-17T00:00:00.000Z
Notice that in this second request we set the date to 2023-06-13T00:00:00.000Z which captures tasks (completed and incompleted) since/after 2023-06-13T00:00:00.000Z within Section 123.
If you would still like to use this particular endpoint (Get multiple tasks) to get incompleted tasks since <YOUR_DATE_TIME> then you could ask for the (i.e. completed property) in the opt_fields and do client side filtering after you received the response.
Thank you @John_Vu , I just tried it, and now it seems to work as expected, in projects AND sections.
That’s what we use in Bridge24,
to get “incomplete” tasks, we use ?completed_since=now.
And, to get all, we use ?completed_since=1900-01-01. (or no parameter)
That was working for /projects/xxx/tasks, but not for /sections/yyy/tasks".
But, I just tried that again, using /sections endpoint, and it seems to work fine now!
I am sure something have been fixed since, because it was not working yet a few weeks ago.