It often happens that I specify a task quite carefully, and then when I think about the next task, that ask is dependent on the previous task being done.
I’d like to be able to continue my flow and type up the task and queue it to be done after the previous task is done and merged, somehow.
I’m not sure what the UX flow would be for this. Perhaps the way I’m imagining it is not optimal. The key requirement is as a user I want to be able to lay down several tasks that are clearly specified and delineated, but depend on each other, and be able to not keep them in my mind (or in an unsaved textbox) until the previous task is done.
Perhaps this could be done with a “Enqueue task” button that then prepares a task but doesn’t start it yet until you manually decide to start it. Or I could make it dependent on another task being merged. I don’t know, up to you. But I feel like I’ve articulated the user need there.
Hope this helps!