I think either way works for me. There would need to be some way to configure the view of subitems, so they didn’t flood my boards (I would have a lot… haha) but just a checkbox showing “Include subitems” would be enough.
I’m not sure how the structure would look codewise, but in my head it makes sense that subitems would probably be simpler in the long run. (Calendar view, assignees, etc.)
I ended up not using it anymore. There was too much management and not enough reminders for the function added.
Essentially what you do is create another folder and create brand new items (each item being a new subtask), and then link them to the original item that you were working on. That way each subtask, as a full-fledged item, has customizable attributes and details.
Is this still the recommended way of creating subtasks? To me, it seems very convoluted and actually doesn’t work properly anyway, because the subtasks do not stay checked once someone marks them completed.
Our current workflow is to create “task templates” which consist of a main task with lots of subtasks. Each time the task needs to be done, we make a copy of the task template and assign it to whoever is doing the task.
Creating those task templates will take an eternity with this method and we currently won’t have an accurate idea of which subtasks have been completed because they don’t stay checked.
Hi @adam3 First of all, welcome to the community, we are happy to have you here
Regarding the subtasks - yes, I would say that this is still one of the most recommended ways of creating subtasks.
The other simpler version of this would be to use “checklist” attribute which will allow you to add values to the checklist and tick them off whenever you are done with a certain “subtasks” but it removes the ability to assign someone to it, to add a date to it, add attachments or whatever else you were wishing to add. With checklist each individual item you create can have its own custom checklist that you can check / uncheck as you go through the stages.
Good news are that we are actually moving forward with your “sub item” feature - which will help you create proper subtasks, maintain and control everything in just one folder - it’s already in the “to do(ready)” column so that can be expected in the upcoming months
The only thing stopping me from using the checklist attribute is that some of the subtasks need further explanation than just a one-liner, so a full “subtask” attribute would be really useful.
I completely understand, for now I would stick with the “subfolder” idea as that works for most people who are in need of this sub task/item feature.
