[bug] TaskNotes Feat

[wedgen]

Issue

Testing the new TaskNotes integration fails to prove a task in the task view.

Debugging

I have added the task tag to the front matter:

---
tags: [task]
---

• I have tried this with and without the [] and with #task, neither produce an entry in the task view.
• I have attempted to use the Task in Folder command, which does not produce a file in the desired folder and no error (I can't see how to bring up the developers console, ctrl + shift + I doesn't bring it up)
• When attempting to set the "default task location" (or any of the default locations) the buttons do not produce any output.

What does work

:newtask /folder/location does indeed create the task with all the appropriate frontmatter, but does not appear in task view.

Expectation

tagged task notes appear in task view
Tasks are created with Task in Folder command.
Default [drawing, database, tasks] location are mutable

[adibhanna]

Thanks for the detailed report. I dug into each part and pushed a fix for the settings piece; the task-view piece I could not reproduce, so I need a bit more from you.

Fixed: the default location settings now stick (c2f8c21)

You were right that the "New Drawings, Databases & Tasks" location controls did nothing. Root cause: the backends were silently dropping those settings on save.

• Self-hosted / web build: the Go server's settings model had none of drawingsLocation / databasesLocation / tasksLocation, and Go drops unknown JSON fields, so on the web build all three reset on every save. That matches your "any of the default locations do nothing" exactly, and (together with devtools not opening for you) suggests you're on the web/self-hosted build. Is that right?
• Desktop: the tasks location specifically was dropped by the settings sanitizer (drawings and databases were kept), so it snapped back and new tasks always landed in the inbox.

Both now round-trip correctly, verified with tests on each surface plus a live POST/GET against the server's settings endpoint. This also explains the "New Task in Folder" behavior: a file was being created, but with the location setting not sticking it went to the inbox rather than where you expected.

Could not reproduce: task files not appearing in the Tasks view

This is the part I need help with. In the current code, a note tagged as a task does appear in the Tasks view. I checked both surfaces:

• Desktop: a note with just tags: [task] and one in a subfolder both show in the Tasks view.
• Server (/tasks): it returns the task file for every tag form you tried, tags: [task], bare tags: task, a block list, tags: [work, task], and tags: ["#task"].

So detection and scanning look correct. A couple of things that would help me pin down what you're seeing:

1. Which build and version? (Desktop macOS/Windows/Linux, or the self-hosted web/Docker build, and the version number.)
2. Where does the task note live? The exact vault-relative path, e.g. inbox/Foo.md vs SomeFolder/Foo.md, and whether your vault is in "inbox" mode or "root" mode (Settings, Vault). A task file placed in a top-level folder that sits beside the notes area in inbox mode is the one spot that would not get scanned.
3. Does hitting Refresh in the Tasks view (or reopening it) surface the task?

If you can share those, I will get the rest sorted. The location fix ships in the next release.

[wedgen]

I'm currently on 2.15.0 on Desktop (windows, lastest as of this morning though i see there's a new release but installables are not ready yet), my self hosted image is 2.14.0 (latest pull as of 7/23/2026)
I have closed and re-opened zennotes several times, refreshed task view, I have even rebooted, i have restarted the self-host docker image.
Could there be a configuration issue from an update that would block this functionality?

Here are screenshots showing the lack of tasks even though the note is tagged.