Date constraints after drag and drop not applied

Bug #1036695 reported by Izidor Matušov on 2012-08-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Getting Things GNOME!
Critical
Bertrand Rousseau

Bug Description

Steps to reproduce:
1) Create two tasks: a (due: tomorrow) and b
2) Drag and drop b under a

Expected result: Task b has due date tomorrow.

Actual result: Task b has no due date. It doesn't help to open task b. Hower, when you open task a, the due date of task b is updated.

Related branches

Izidor Matušov (izidor) on 2012-08-15
tags: added: regression
Izidor Matušov (izidor) on 2012-08-15
Changed in gtg:
importance: High → Critical
Nimit Shah (nimit-svnit) wrote :

Just a guess but this can be solved when start and due dates are updated on dragging and dropping a task into another.

Nimit Shah (nimit-svnit) wrote :

Drag drop is handled in liblarch.
    Liblarch considers all the entities (task, tag) as same, hence we can't hard code liblarch to update the dates of child element according to that of parent element.

tags: added: liblarch

Is there some kind of hook in liblarch allowing to execute some code from outside liblarch when a drag & drop happens?

Izidor Matušov (izidor) wrote :

No, there is none. It should be added for the next release. However, this bug was introduced by modifying date things in GTG, not in liblarch. If it could not be solved easily, we should postpone this bug.

Changed in gtg:
assignee: nobody → Bertrand Rousseau (bertrand-rousseau)
status: Confirmed → In Progress
Changed in gtg:
status: In Progress → Fix Committed
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers