Right now, Quire supports only a single type of subtask, one that is treated (relatively) independently with respect to the original subtask.
What can be done is a second type of subtask can be introduced: one that is integrated with the parent task. The new subtask would be counted as a part of the main subtask, and completion of all subtasks in a parent task would lead to completion of a parent task. In addition, this would also cater to a number of other pending feature requests. (For example, #4110 and #3935) It would also help maintain the uniqueness of Quire by allowing infinite sub levels
@Walter_Kawecki In my personal experience, I have found separating tasks and subtasks rather useful, although I would agree that the current subtasks should be rebranded in anther form.
Regarding the Kanban board, often there are subtasks which are rather independent of the parent task (take for example a grocery list: I may have completed a part of the list, but I certainly wouldn't have completed the entire list). However in the same vein, I find myself frustrated at viewing dependant tasks in the Kanban board.
Monish, Mar 31, 2021
+1
Adriano Labate, May 21, 2021
I also commented something similar in my feedback #4252
Ketlin Milani, Mar 26, 2021
Yes, i would like this option as well. This is a good solution. If implemented then hopefully the subtasks that are fully connected to parent tasks won't show up all over the place in the kanban board. Maybe they won't show at all unless you click the parent task or something then they will show under the parent task.
(deleted-x5AM), Mar 26, 2021
Also, without actual subtasks, Kanban view is useless.
@Monish I'm commenting here days later because I'm in the process of moving these stories back to Clubhouse.io, the tool we had been using, for this specific reason.
Also the UI is really hard on the eyes - you need more contrast / shapes so a user can instantly intuit features, functions, and actions.. This is a utility, not a "beautiful iOS app"
WJK, Mar 31, 2021
@Monish What you're describing here IS a subtask.
What you call subtasks ARE NOT SUBTASKS> they are weeird and super not intuitive.
BY DEFINITION, subtasks should be children of parents. ("Sub" means: subordinate, subservient, under -- https://www.etymonline.com/word/sub- )
You should just kill the current functionality or retool it and call it something else because they are not subtasks.
Again, a sub-task BY DEFINITION is the child of a parent.
WJK, Mar 31, 2021
Yeah, I did have that use case in mind too. @Ketlin-Milani had also mentioned the requirement of having parent tasks show the status as a percentage of tasks completed. Two different types of subtasks would also help there.
Monish, Mar 26, 2021
+1
Ralf Ebel, Mar 26, 2021