Get tasks API.

[Boon Hian TEK]

Hi,

First of all, thanks for this great app! Been using it like a
lifesaver for about 4 months now.

Anyway, I wrote a simple script to pull down tasks from one specific
checklist and then generate a daily email to myself and a colleague.
Since we keep using the tasks and just mark off those that we no
longer need, the list itself keeps growing bigger and bigger.

Is there a way to retrieve via the "/checklists/checklist_id/tasks.
(json|xml)" API to pull down only "active" tasks?

Thank you very much!

Best regards,

Boon

[KIR]

Hi Boon,

First of all, thanks for this great app! Been using it like a
lifesaver for about 4 months now.

  You're welcome :) . I'm really glad you like our tool.

 

Anyway, I wrote a simple script to pull down tasks from one specific
checklist and then generate a daily email to myself and a colleague.
Since we keep using the tasks and just mark off those that we no
longer need, the list itself keeps growing bigger and bigger.

   So, if I understand correctly, you close or invalidate completed items, and use

  "hide completed" mode?

 

Is there a way to retrieve via the "/checklists/checklist_id/tasks.
(json|xml)" API to pull down only "active" tasks?

   I can add a kind of filter for "status" parameter. How large is the list by the moment?

   So far, you should be able to filter the tasks using status attribute.

 

   Kind  regards,

   KIR

[Boon Hian Tek]

Hi Kir,

On Sun, Jun 14, 2009 at 9:08 PM, KIR <kirill....@gmail.com> wrote:

Hi Boon,

First of all, thanks for this great app! Been using it like a
lifesaver for about 4 months now.

  You're welcome :) . I'm really glad you like our tool.

 

Anyway, I wrote a simple script to pull down tasks from one specific
checklist and then generate a daily email to myself and a colleague.
Since we keep using the tasks and just mark off those that we no
longer need, the list itself keeps growing bigger and bigger.

   So, if I understand correctly, you close or invalidate completed items, and use

  "hide completed" mode?

Exactly.

 

Is there a way to retrieve via the "/checklists/checklist_id/tasks.
(json|xml)" API to pull down only "active" tasks?

   I can add a kind of filter for "status" parameter. How large is the list by the moment?

   So far, you should be able to filter the tasks using status attribute.

Well, the list is currently not big at all, hence, manageable by filtering via the status attribute. I am starting to wonder if this is the correct way of using the list, or should I delete the finished tasks. Otherwise, eventually, the tasks will become quite unwieldy to be downloaded etc.

What is your recommended usage pattern?

Again, thank you very much for Checkvist and your amazing response time!

 

   Kind  regards,

   KIR

[KIR]

>>> Is there a way to retrieve via the "/checklists/checklist_id/tasks.
>>> (json|xml)" API to pull down only "active" tasks?
>>
>>    I can add a kind of filter for "status" parameter. How large is the
>> list by the moment?
>>    So far, you should be able to filter the tasks using status attribute.
>
> Well, the list is currently not big at all, hence, manageable by filtering
> via the status attribute. I am starting to wonder if this is the correct way
> of using the list, or should I delete the finished tasks. Otherwise,
> eventually, the tasks will become quite unwieldy to be downloaded etc.
>
> What is your recommended usage pattern?

Well, Checkvist loads all non-deleted tasks both in WebUI and via API.
So if you'll be adding tons of tasks and instead of deleting
completed tasks you'll only hide them,
this may add some slowness.

But I believe, that there is no actual problem. I use this approach
for myself for several checklists, and didn't notice a problem yet.
But, I have only ~300 tasks per checklist at most.

If you notice a slowness, you can always review completed tasks and
remove ones not needed anymore.

>
> Again, thank you very much for Checkvist and your amazing response time!

You're so welcome :)

Regards,
KIR

>>
>>
>>    Kind  regards,
>>    KIR
>>
>>
>>
>
>
> >
>

[Boon Hian Tek]

  Well, Checkvist loads all non-deleted tasks both in WebUI and via API.
 So if you'll be adding tons of tasks and instead of deleting
completed tasks you'll only hide them,
 this may add some slowness.

 But I believe, that there is no actual problem. I use this approach
for myself for several checklists, and didn't notice a problem yet.
But, I have only ~300 tasks per checklist at most.

 If you notice a slowness, you can always review completed tasks and
remove ones not needed anymore.

>
> Again, thank you very much for Checkvist and your amazing response time!

 You're so welcome :)

Hi Kir,

Okay, great. Now I just need to slightly adjust my expectation and usage pattern.

Cheers,

Boon