Date structure of tasks and subtasks

Asked by Nimit Shah on 2012-05-25

Hi!
    I had been working on the date constraints bug: https://bugs.launchpad.net/gtg/+bug/826916 and the question asked related to it https://answers.launchpad.net/gtg/+question/197755.
   I was confused at one point:
     we have a task structure
       A (some due date)
         -B (no due date).
  Now as discussed, my code did not update the due date of B when due date of A was updated. But, when we call get_due_date for B. It would return the due date of A as it returns the most urgent due date of it's parents. As a result, the due date of B will not be refreshed in the task browser after updation of due date of A.
   But, then when we update some attribute of B, Bs due date will be updated to that of A.

   So, my question: should get_due_date return the most urgent due date of all it's parents. If yes then why not update the due date of the child when due date of the parent is updated? Because, I feel it is a bit odd that get_due_date would return something else and actual due date would be something else.

Question information

Language:
English Edit question
Status:
Answered
For:
Getting Things GNOME! Edit question
Assignee:
No assignee Edit question
Last query:
2012-05-25
Last reply:
2012-05-25
Izidor MatuĊĦov (izidor) said : #1

My opinion is that due date of child should be updated. Due date should be propagated both ways (up and down), and if not set, it should be set. On the other side, start date should not be propagated or set. (A child can have any start date regardless it parent.) The only thing to care about is that start_date <= due_date.

Can you help with this problem?

Provide an answer of your own, or ask Nimit Shah for more information if necessary.

To post a message you must log in.