Tasks in projects are added under the root title

[ndreux]

Describe the bug

In Things, when a task is part of an area, it appears as such when synchronising with Obsidian: the task is below the area subtitle.

If a task is in a project (not directly in an area), when synchronising with Obsidian the task is put below the root title of the note and not under the project subtitle.

Steps to reproduce

1. In Things, create an area
2. In Things, create a project under that area
3. In Things, create a first task and assign it to the area
4. In Things, create a first task and assign it to the project
5. In Things, mark the tasks as done
6. In Obsidian, sync the logbook

Expected behavior

A clear and concise description of what you expected to happen.

• I would expect the project to appear as subtitle of the area.
• I would expect the task assigned to the project to appear below the project subtitle

Screenshots

Setup in Things

Current behavior

Expected behavior

Environment (please specify)

OS

Mac OS 11.6

Obsidian Version (e.g. v0.10.6)

v0.12.15

Plugin up-to-date

[djbowers]

I don't know if I would consider this a bug, maybe a feature that hasn't been implemented yet, but I think this would be really helpful in connecting projects between Things and Obsidian.

[beastlybeast]

Came here to post this. I find it jarring, when looking through the logbook, when only things that are directly under an area, and NOT an area-->project, and NOT just a project, appear to have a sub-heading in the logbook. The end result is that headings just seem to randomly appear throughout the logbook, based on which items I happen to have nested under an area but not a project.

In this example, "Journal" and "Process personal email" belong to the "Daily" project and the "Routines" area, but only the task I have nested under "Family" that is without a project showed a heading.

Some ideas that I would consider solutions, as new features:

1. A setting to disable sub-headings entirely -- so only tasks show in the logbook, with no reference to their areas or project headings. (easiest to implmement)
2. As ndreux described
3. Instead of headings, just prefix tasks if it has an area and/or project: "Area | Project | Task" or "Area | Task" or "Project | Task"
4. A combo of the above: Group headings by Area, and then prefix project name

Another idea that would be more of a "bug fix"

• Show a heading for Area even when a task has both an Area and a Project