How do people set up their boards for managing progress of tasks/requests when trying to use Subtasks? We have our board set up with a To Do, In progress, done kind of set up. But when using subtasks we cannot separate the subtask from the main ticket and move them along individually. So I’m looking to create a separate status field and then have the board itself labeled differently. I just don’t know what that is yet.
Hi David, I understand. The subtask feels tied to the parent task.
Since subtasks don’t automatically show in the project views, you must add them to the project first. Once added to the project, the subtasks will appear as independent cards that can be moved across the columns, allowing you to track their progress alongside parent tasks.
If you want to make it easier, you may also add a rule in the project: when a subtask is created, add it to this project
Thank you for responding. I understand that subtasks can be added to the project so they appear as independent cards. However, that is not really the core issue I’m trying to solve.
My project board has sections labeled To Do, In Progress, and Done. If I create a parent task in To Do and then add 3 to 4 subtasks under it, I want to move each subtask independently across those sections, similar to an Epic and child task relationship.
Right now, the subtasks remain tied to the parent’s section and cannot be progressed independently on the board. That is what I am trying to achieve.
My original question was really about design approach. If using To Do, In Progress, and Done as board sections does not work well with subtasks, then is there a better structure I should be using?
For example, should sections represent something else entirely and status be driven by a custom field instead? If so, how are others structuring their boards to handle parent and child work cleanly?
Does that make sense?