How does tags compare to tasks here? You mention that bases are unable to read file contents, but they are able to extract tags that are not in a property (I don’t use tags in properties and my bases can show them).
How are tags treated differently here than tasks?
From what I can see in the Dev Tools, tags (either in Properties/Frontmatter or in a note’s content) are stored as “a whole”/“their own thing” in the cache of a file 
…
I mean, they have dedicated places in the cache/Obsidian’s API (They have a dedicated Properties key, a dedicated pane, etc…) .
Note content checkboxes/tasks list don’t (not really)…
All the cache stores for checkboxes/tasks list items is, in a way, if the item in a list is “a task or not”, what characters sits between the 2 square brackets of the checkbox and the position of the checkbox/task in the note…
So none of this would really represent what’s relevant for a task: the info you write after the checkbox/task : a potential due/schedule date, some context, etc… which is part of the note content Obsidian can’t access.
Said somewhat differently, all Obsidian stores/sees in the file cache of a note regarding list is that in said section in the note there could be list and that its items could be checkboxes/tasks (with a potential specific character between the squared brackets).
(I’m no dev though 
… I’m just playing around with Obsidian API in the Dev Tools 
)
Let’s be frank, tasks in Obsidian are over simplified.
A better way to manage tasks are kanban lists, you add more context all in a compact view and organize, re-arrange as you like.
Still, both methods are inadequate and can’t deal with complex tasks with set durations and priorities to reach milestones in projects.
Here is my article:
Gosh I need this feature so bad. I just want to access the checked and unchecked task in a note so my folder homepage would be complete.
Not sure if I’m just layering on, but am slightly tearing my hair out. I work in a corporate environment where Obsidian is approved, but not community plugins. As such, I can’t utilise the obvious things that would help me here. Specifically, I create tasks throughout the day in my daily notes and in individual project notes, some of which belong to me and some of which I have delegated to my team.
What I really need to be able to do is, when I’m having a meeting with Bob Smith or Pauline White, pull up my “Bob Smith” or “Pauline White” notes, and display a list of open actions assigned to them, whether they are in a daily note on an ad-hoc discussion I’ve had with them, or whether they have arisen in a project. I take it that is not feasible without Dataview or Tasks plugins, using vanilla Obsidian, only?
If you made each task its own note, had a way of denoting it was a task (property or tag), and have a property called something like “assignee”, you should be able to have a base that takes advantage of the this object. Then you embed that base that checks that the assignee matches the embedding note.
Interesting. I think I’ve seen something to that effect, but thought I still needed something else. Will investigate! Thank you!
I use tasks and checklist items a little differently. Using the minimal theme, I’ve created a system where the different statuses of checklists means something to me. These are just two examples.
When I’m going through a book note, I can pull out to-dos, questions, things for reference, ideas…all using different types of status.
I was wondering if that would be possible in bases. Bases seems to work at note level and not the block level. Dataview looks for inline properties and tasks. My assumption is that bases won’t be able to look at block level and I’ll still need to use Dataview.
I came here to see if anyone found a workaround.
thank you for your response!!! we appreciate it immensely 
what if there was a way to supply a custom data source for bases views while defaulting to existing behavior (reading from frontmatter)?
I would love to see this as well. It’s probably something that’s not trivial to implement once you start thinking it through but it’d be highly valuable to me.
It would be amazing for many tasks plugins (and for bases) to have that information available without all resorting to custom parsing and indexing. As for having tasks as a legit source for bases, I can already imagine how cards, kanban, gantt, or other view could be used to present them, and expression columns to create custom priorities or grouping. So many possibilities.
