taskyaGTD - Yet Another Getting Things Done. - Tasks: task #6591, Tasks dependencies

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

task #6591: Tasks dependencies

Submitted by:  MiKaël NAVARRO <klnavarro>
Submitted on:  Thu Apr 16 07:33:19 2009  
Should Start On: Fri Mar 20 00:00:00 2009Should be Finished on: Thu Apr 16 00:00:00 2009
Category: NonePriority: 3 - Low
Status: Need InfoPrivacy: Public
Percent Complete: 0%Assigned to: MiKaël NAVARRO <klnavarro>
Open/Closed: OpenEffort: 0.00

Wed May 13 09:33:15 2009, comment #2:

Hi Matias,

> do you have any insight on the dependson thing?

I am not convinced by the need of this functionnality, it is really useful?

The GTD method focus on next action to do and do not depend on order of tasks; but tasks are grouped by project.
This is the daily review that determine the next actions to do...

In addition I want to keep the txt file as simple as possible, I don't want introduce sections in the format of the file. You must keep in mind that the file can be read with a simple editor (like emacs) and that searchs can be performed by hand (grep) from a shell.

I am afraid that this functionnality complexify the usage and the maintenance of yaGTD (http://en.wikipedia.org/wiki/KISS_principle)?

MiKaël NAVARRO <klnavarro>
Project AdministratorIn charge of this item.
Wed May 13 09:30:11 2009, comment #1:

Hi MiKaël,
I have done a bit of what I wanted. The tasks have now the attribute
dependson, which is a list of integers. It appears with the char O in
'ls'. This is not completely nice for me; it has two problems:

a) the priority is not changed. The computation of priorities is done on
a task basis, and tasks do not know which ones depends on them. I can
add a new property for tasks, 'dependedby' or something like this, but
it does not look like a good solution.

b) if you change the todo.txt file by hand, you can completely corrupt
the dependencies, since the only info I have for dependencies is their

Maybe both problems could be solved by adding, at the end of todo.txt, a
list of dependencies, not by number, but by title. Something like

------------------------ todo.txt ---------------------------
Talk to boss U:1 I:3 T:1H S:2009-03-05
End nice project p:nice U:4 I:3 T:1H S:2009-03-05
Begin odd project p:odd U:2 I:2 T:5M S:2009-03-05

Begin odd project
End nice project
Talk to boss
End nice project
Talk to boss
------------------------ todo.txt ---------------------------

I'm sending you the yagtd.py and gtd.py that I have so far. They have
marks as
# Matias beg
new stuff
# Matias end
which I put for finding new additions easily. Of course, I will
delete those marks when they are not needed anymore.

Best regards,

MiKaël NAVARRO <klnavarro>
Project AdministratorIn charge of this item.
Thu Apr 16 07:33:19 2009, original submission:

I am new to GTD philosophy and this might be "heretic", but this is what i'd love to have: a "depends_on" field. Suppose you have a task, say #3, but you first need to finish say #8 and #13 before doing #3. It would be great if one could do:
GTD> dependson 3 8,13
and this would appear as:
3: this is task 3 @nowhere U:2 I:4 D:8,13
then this would put a higher rank to #8 and #13. The dependson field would appear as long as tasks 8 and 13 are not done.

Is this 'doable' in yagtd? If you think this would not break the gtd philosophy, I could try to add it to the code.

Best regards,

MiKaël NAVARRO <klnavarro>
Project AdministratorIn charge of this item.


Attached Files
file #5777:  gtd.py added by klnavarro (14kB - text/x-python - Prop. on dependson)
file #5778:  yagtd.py added by klnavarro (34kB - text/x-python - Prop. on dependson)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by klnavarro (Submitted the item)
  • -unavailable- added by klnavarro (Initial submission)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed May 13 09:33:30 2009klnavarroStatusNone=>Need Info
    Wed May 13 09:31:31 2009klnavarroAttached File-=>Added gtd.py, #5777
      Attached File-=>Added yagtd.py, #5778
    Thu Apr 16 07:33:19 2009klnavarroCarbon-Copy-=>Added -unavailable-
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup