A simple way to add chained tasks

[pcause]

One persistent request people have is to have chained/dependent tasks. These systems can get very complex and evolve into full project planning tools, but for many of the comment use cases there is just a after A do B then C type use case. I've thought about this in the context of this plugin and have a suggestion for what might be a not too difficult way to implement this in this plugin and obsidian.

In this description I am going to use the terms first tasks and next task so you know which I am talking about.

When we want to link a first task to a next task there would be a new emoji and the link to the next task. The link is a block link to the the block which is the next task. The 2 tasks are now linked.

When the first task is completed we need to make the next task active and for that we need a duration. We would have a duration icon in the next task with a specification of length (3 days, 2 hours, 1 year, etc). When initially creating a next task one would enter the duration emoji and then the length. No start or due dates are entered, just a duration. When the first task is completed a start date of the current day is added to the next task, and a due date is calculated for the task based on the start date and the duration.

There is an issue of whether or not the start date should be the day of completion of the first task or the next day. I like the day of completion of the first task because this sets the stage for when we might add times to tasks and hence if I have something that is 3 steps and each an hour long, if the start date of the next day is set to the completion date for the first task, I get a new task for that day. When/if times are added, next task would get a start/end time for the day the first task was completed but at a time of day based on when the first task was completed.

[claremacrae]

Hi, do you see this as a feature request or a topic for discussion?

If it's a feature request, please create a new-feature issue for it, filling in the form - and I will lock this one, linking to the issue.

If it's a topic for discussion, I'll convert it to a General Discussion. And if it comes to any firm conclusions, a new-feature issue can be created to describe the actionable steps requested.

Using Discussions for actionable work has been a nightmare for me, for tracking tasks in this project, hence my renaming Ideas, to try to make it clear that I don't want any new Ideas created in discussions.

[pcause]

sorry, i thought you wanted new feature requests made through the discussions. i'll create a feature request.

[claremacrae]

Thanks, yes that was wanted for a long time, you are correct. Discussions are missing a lot of features that Issues provide.
No problem at all!

Note for others, this has moved to: #1378