Skip to content

path-based project mapping not working for tasks parsed from file metadata or tag-based #358

@ggiammat

Description

@ggiammat

I'm experiencing an unexpected behavior with tasks parsed from file metadata or based on tags. When the path-based project mapping is enabled, tasks parsed from file metadata or tag-based will not get the automatic project assigned.

From an empty Vault with only Task Genius 9.1.5 running, I enabled parsing of task from file metadata and I also enabled a Path-based Project Mapping as can be seen below:

Image Image

Then I created two files under the FOLDER_1 folder:

  • My First Task.md has a the #task tag, so it is parsed as task by TG
  • Second File.md is a normal file with a checkbox that is parsed as task by TG
Image

Since both files are under FOLDER_1, I would expect that for both of them project_1 is assigned as project, but in reality My First Task has an empty project.

Image

Briefly looking at the code, I see that for tasks parsed from file metadata and tag-based, the tgProject metadata is never populated. I do not know if this is wanted or if adding this would have other side effects that I'm not considering right now, but for my use case, I would like to have also tag-based tasks to get the automatic project populated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions