GTG

Tag tree work incorrectly

Bug #348606 reported by Laurent Peuch
4
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Low
Unassigned

Bug Description

The feature that tag surbtask when you tag a task seems completly buggy. I've tryed to reproduce something twice but the result change. It seems that, opening a new subtask one time change the fact that it will be tag or not if you tag it's parent.

A picture will discrib more the problem: http://pix.nofrag.com/d/a/6/7a15525de004150d7849937cba863.png

Here I've start by tagging the top tag "Administration système". Then I've tag "lancer le projet" then "Amener tout le monde a travailler sur launchpad". You can see that subtask are not tag identically.
Btw the first time I've done that, "Burton" and "Installer FAI" was tag. I remove the tag by hand in the files before I tryed to reproduce the bug.

Revision history for this message
Laurent Peuch (psycojoker) wrote :

Addition:
Juste after a xkill the subtask that have appear to be automaticly tag are now untag.

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

The principe is simple : we cannot modify an existing task. We cannot add a tag to all the children recursively because it might not make sense at all.

But, when you create a subtask, by default the subtask takes the tags from its parent. There's one subtilities there : if you add a tag immediatly after adding a subtask, the subtask will inherit the tag.

It's really convenient from a functionnal point of view, the only problem is that it's not intuitive. So it must be changed or better documented.

Revision history for this message
Laurent Peuch (psycojoker) wrote :

It's make more sense now. If you chose the documentation way you can add it in the initial task on learning how to use GTG.

I can confirm you that there is still a bug: when you restart GTG the automatic tag subtask aren't tag anymore.

Changed in gtg:
importance: Undecided → Low
status: New → Confirmed
Changed in gtg:
milestone: none → 0.1.1
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

As suggested, I added some explanations in the initial tutorial.

fixed in rev. 225

Changed in gtg:
assignee: nobody → ploum
status: Confirmed → Fix Committed
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.