Nested tasks should inherit their parent item/note affiliation
Having recently migrated from Roam, I was trying to find a way to compile notes and tasks from multiple project on daily jots, but have been frustrated that tasks are not tagged/linked to projects in that way.
Lets say I am having a team meeting, in which I run through all projects and want to quickly note down tasks linked to their project tags or notes.
If I use backlinks to the projects and nested tasks in the daily-jots text ( https://imgur.com/a/wULrcjL ), I can see the tasks in the backlink view in notes, but in "task view" I lose the context of the project I listed them under, unless I inline tag every single task ( https://imgur.com/a/TgTM7sJ )
Ideally the the task nested under a project in daily jots or notes would inherit a dependency or tag from the parent item/project, thus allowing easier filtering in "task view".
It would be so useful to see in some way in Tasks view the relationship between parent task and those nested under it! Because the nested tasks are related to their parent task, that parent task description often contains contextual information that is relevant for understanding what the subtask itself is about. It feels unnecessarily cumbersome having to repeat same things in both the nested task and the parent task, just so that the nested task makes sense when viewed in isolation in Tasks.
It would also be useful to have a quick filter in Calendar view that would allow toggling between "show all" and "show only parent tasks". Or have some other way to make it clear which parent task a subtask is related to. At least in my case, from scheduling point of view, it's more useful to know what project/context to work on instead of the more minute subtasks related to it. Although this might be one of the highly personal things that only apply to me :)
To add to this, when in Cal view, perhaps a good way to indicate that a parent-task is currently "waiting" for a nested subtask to be completed first is to put a small yellow (!) icon next to it (and maybe make the text greyed out?), and when you hover or click on the (!) it lists the subtasks that the parent-task is dependent on
It would also be handy to have a filter option to hide the parent-tasks that are currently in a "waiting" state. (and when the nested subtask(s) is completed then the linked parent-task has its "waiting" state removed automatically)
This allows you to glance through the large heap of project tasks and quickly gleen which tasks are (or aren't) actionable right now, and then can easily drag and drop the right tasks into your calendar without having to stop and think if the task ready to be worked on now or not
Right now Amplenote is extremely effective for personal tasks, but until this sorta functionality is in place it's hard to commit to for project tasks
^ This idea above comes from the philosophy that the best way to get huge long term projects done is to break everything down into many little actionable tasks.
However the biggest resistance barrier to even doing the task OF "breaking down the tasks" is then trying to constantly sift through all the tasks and consciously try figure out how to schedule it all in, and in what order. This is ESPECIALLY difficult when you're a one-man team that wears ALL of the hats of a small business: production, web design, SEO, graphic design, client relations, social media, publishing, promotion, etc etc. All the tasks within those roles add up and very often depend on other tasks in various areas being finished first. This is where Amplenote would be the ultimate solution if tasks had dependency relationships/links to each other and you could then filter based on those relationships
Finishing a sub-task which then automatically reveals its parent-task in my Cal view sounds like a dream come true
And maybe a good way to edit task dependency data could be: When in Task/Calendar View, you click the down-arrow to expand a task, there's a field called "Dependent on:" and then you can select/link a task? And then it becomes a subtask.
And then that's what gives the corresponding parent-task a small yellow (!) and puts it into "waiting" state.
And maybe the "waiting" state is automatically applied when you input/create nested subtasks via Note editor too. (with the  method)
And maybe subtasks that are currently holding parent-tasks to a waiting state get a little boost in Task Score too, to indicate extra importance. (not essential though, just an idea)
(sorry for the triple post!! thanks for your time!)