Tasks: sub-tasks inherit task properties

Created on 23 Jan 2020  Â·  8Comments  Â·  Source: tasks/tasks

Most helpful comment

I'm a new user and am very happy to make the switch from a closed, proprietary application to one that is FLOSS and well-made. Being able to define recursive subtasks is very useful.

I think a subtask should be inextricably* linked to its parent. This is what that would entail:

  • Completing a parent task would automatically complete its subtasks and force any recurrences (of the subtasks) to end.

    • If the parent is set to recur then this would apply to every recurrence of the parent. A recurring parent would recur with its subtask tree intact and set to its initial state.
    • Similarly, when all subtasks of a parent are completed, the parent's status is automatically set to completed. If the parent is recurrent then this would end the current recurrence (and complete all the subtasks in that recurrence).
    • Probably makes sense to disallow "forever" recurrence in a subtask, I can't think of a use case in which a subtask would recur infinitely within a single recursion of its parent.
  • The start and due dates of a subtask should be within those defined in the parent – subtasks could be (optionally) made to default to the start and due dates of the parent.

    • If a date in a subtask is set to be outside the period defined in its parent then the corresponding date could be automatically adjusted in its parent (and ancestors, recursively, if needed).
    • Similarly, recurrence of a subtask should end on or before the parent's due date and/or the parent's due date adjusted automatically to be the date when the subtask's recurrence ends.

*I realize that a subtask can be detached from its parent and moved around. What I mean here is that as long as a parent-subtask relationship exists, the relative consistency between their attributes should be maintained.

All 8 comments

When a task is given a date or hidden etc, the sub-tasks should get the same by default. Currently, if I hide a task, all the sub-tasks appear in the list of tasks

Try toggling on 'Tasks settings > Show subtasks', when this is enabled then subtasks will also be hidden

Thanks.

'Tasks settings > Show subtasks', is enabled. To show problem:
Create new task. Set date.
Create some subtasks using the same form
select hide using same form
select save
Task list now shows all subtasks in list but hides main task. The result is if main task is 'purchase widgets' and subtasks are 'get supplier price', 'complete purchase order' only the subtasks appear in the list so there is no context and no way to separate from other 'get supplier price' and complete purchase order' subtasks.

If subtasks can inherent attributes from main task then by default they would have same date and hide status.

Regards Craig

--
Craig Tipping,
When you stop learning, stop listening, stop looking and asking questions, always new questions, then it is time to die. - Lillian Eugenia Smith

-------- Original Message --------
On Jan 23, 2020, 21:32, Alex Baker wrote:

Try toggling on 'Tasks settings > Show subtasks', when this is enabled then subtasks will also be hidden

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry, I see what you're saying now. I'm going to have to think about how to solve this

I may add to this request that subtasks also need the same tags as it's parent. If not, all subtasks appear in the uncategorized section, but not it's parents. What do you say?

Yes. I didn't think of that.

One other thing is tasks created without using the normal entry screen, say from being synchronised or as a sub-task don't get the defaults applied. Can those properties also be transferred?

Thanks.

Regards Craig

--
Craig Tipping,
When you stop learning, stop listening, stop looking and asking questions, always new questions, then it is time to die. - Lillian Eugenia Smith

-------- Original Message --------
On Mar 1, 2020, 22:40, Lucas wrote:

I may add to this request that subtasks also need the same tags as it's parent. If not, all subtasks appear in the uncategorized section, but not it's parents. What do you say?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm a new user and am very happy to make the switch from a closed, proprietary application to one that is FLOSS and well-made. Being able to define recursive subtasks is very useful.

I think a subtask should be inextricably* linked to its parent. This is what that would entail:

  • Completing a parent task would automatically complete its subtasks and force any recurrences (of the subtasks) to end.

    • If the parent is set to recur then this would apply to every recurrence of the parent. A recurring parent would recur with its subtask tree intact and set to its initial state.
    • Similarly, when all subtasks of a parent are completed, the parent's status is automatically set to completed. If the parent is recurrent then this would end the current recurrence (and complete all the subtasks in that recurrence).
    • Probably makes sense to disallow "forever" recurrence in a subtask, I can't think of a use case in which a subtask would recur infinitely within a single recursion of its parent.
  • The start and due dates of a subtask should be within those defined in the parent – subtasks could be (optionally) made to default to the start and due dates of the parent.

    • If a date in a subtask is set to be outside the period defined in its parent then the corresponding date could be automatically adjusted in its parent (and ancestors, recursively, if needed).
    • Similarly, recurrence of a subtask should end on or before the parent's due date and/or the parent's due date adjusted automatically to be the date when the subtask's recurrence ends.

*I realize that a subtask can be detached from its parent and moved around. What I mean here is that as long as a parent-subtask relationship exists, the relative consistency between their attributes should be maintained.

I have been using the app for a Week now and also noticed this behavior. Are there any plans to fix this?
I'm very sorry that I can't help with coding, it'll take some more years for me to be able to understand code well enough..

@akwala makes some good points, for now it would suffice to create subtasks with the same settings the parent task already has.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

chrmaz picture chrmaz  Â·  6Comments

TauPan picture TauPan  Â·  5Comments

aviaryan picture aviaryan  Â·  6Comments

esmoak picture esmoak  Â·  4Comments

JoinGitHub1 picture JoinGitHub1  Â·  4Comments