GTG

Undismissing a subtask (which parent is dismissed too) should undismiss parent

Bug #369890 reported by Arnaud Soyez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Medium
Unassigned

Bug Description

Let's suppose you have dismissed a subtask and its parent. When you undismiss the subtask, it doesn't appear in the task list, but when the parent is dismissed it appears. So the parent task should be undismissed at the same time too.
This is also common sense. :)

Reproduce steps:
- Create a new task, and a subtask in it.
- Dismiss the parent task.
- Undismiss the subtask.

Arnaud Soyez (weboide)
description: updated
Changed in gtg:
importance: Undecided → Medium
milestone: none → 0.2
status: New → Confirmed
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

I think that the parent should not be undismissed. Let's take the example :

- Change the lightbulb
--- Buy a bulb

If I dismissed "changing the bulb" but I suddenly realize that I still need a spare lightbulb, I want the subtask to be undismissed but not the parent.

I think we should simply break the parent relation ship on this case.

Revision history for this message
Arnaud Soyez (weboide) wrote :

It depends on how you see/imagine the hierarchy and dependency.

"Buy a bulb" is a task related to "Change the bulb". That's how you created it and in this exact case you wouldn't need to buy a bulb if you didn't need to change the bulb. But then for whatever reason (other than to change the bulb), you need to buy a bulb, you'll have to add another task for it.

Plus, it makes more sense to me to create a new task for "buy a bulb" if i just need to buy a bulb instead of trying to find it in the dismissed-tasks list and undismissing it.

Devtodo, for example (another todo program I use) also undismisses the category parents, because when you see the tasks list as an XML file, it makes more sense to undismiss the parents.

But, of course, the choice goes to the developers.

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

Fixed in rev. 363

Changed in gtg:
assignee: nobody → Lionel Dricot (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.