You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I've started using Tasknotes recently. After an initial disappointing start, I've got my head around it and I like it quite a bit. Having project-level organization is critical for me. I didn't think this was possible at first but now I see it is. However, I'm having a few problems that might be due to my configuration choices or might just be unsupported functions.
To start with, I'm trying to understand the difference between setting up project suggestions vs metadata sync. Here's my workflow:
I have a folder called Projects which contains one note per Project with core information about the project. Those have a type of "project". The project name is stored in both the filename and frontmatter title.
All my other notes (meeting notes, tasks, etc) have a property called project. That is a list property and contains internal links back to the main project file. I have links set to shortest path possible so these are usually just the project name between double brackets.
In the organization properties of TN, I have project set to use the property key "project". Use parent note is off since usually the parent note is something like a meeting note. For autosuggest filters, I have include folders set to the projects folder, required property key set to "type" and value set to "project". This works as expected - when I go to assign a project I see the files that represent all my projects. Awesome.
Here's the part I'm struggling with; ideally, when I create an inline task in a note that already has the project property set, I'd like the task to inherit that value since it points to the same set of notes as the suggestion filter. I couldn't find a way to do this however. I see that I can set up metadata fields and there's a place to sync fields elsewhere in configuration - but the tasks already have a projects field and I've set it to use my field project, so I don't think re-adding it is what is called for. Is there some way to inherit this value when tasks are created inline in a note with a project value?
I'm also seeing something unexpected if tasks are assigned to more than one project.
Currently, when I group the All Tasks view by my property "project" - I get just what I'd want - groups under just the name of the project. This is true when all tasks are linked to one project. But if I link a task to two projects, instead of showing up under each of them as I'd expect, I get a new group with both values of project, and the project names are the full path.
Is there something I should be doing differently to get the expected behavior ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi - I've started using Tasknotes recently. After an initial disappointing start, I've got my head around it and I like it quite a bit. Having project-level organization is critical for me. I didn't think this was possible at first but now I see it is. However, I'm having a few problems that might be due to my configuration choices or might just be unsupported functions.
To start with, I'm trying to understand the difference between setting up project suggestions vs metadata sync. Here's my workflow:
I have a folder called Projects which contains one note per Project with core information about the project. Those have a type of "project". The project name is stored in both the filename and frontmatter title.
All my other notes (meeting notes, tasks, etc) have a property called project. That is a list property and contains internal links back to the main project file. I have links set to shortest path possible so these are usually just the project name between double brackets.
In the organization properties of TN, I have project set to use the property key "project". Use parent note is off since usually the parent note is something like a meeting note. For autosuggest filters, I have include folders set to the projects folder, required property key set to "type" and value set to "project". This works as expected - when I go to assign a project I see the files that represent all my projects. Awesome.
Here's the part I'm struggling with; ideally, when I create an inline task in a note that already has the project property set, I'd like the task to inherit that value since it points to the same set of notes as the suggestion filter. I couldn't find a way to do this however. I see that I can set up metadata fields and there's a place to sync fields elsewhere in configuration - but the tasks already have a projects field and I've set it to use my field project, so I don't think re-adding it is what is called for. Is there some way to inherit this value when tasks are created inline in a note with a project value?
I'm also seeing something unexpected if tasks are assigned to more than one project.
Currently, when I group the All Tasks view by my property "project" - I get just what I'd want - groups under just the name of the project. This is true when all tasks are linked to one project. But if I link a task to two projects, instead of showing up under each of them as I'd expect, I get a new group with both values of project, and the project names are the full path.
Is there something I should be doing differently to get the expected behavior ?
Beta Was this translation helpful? Give feedback.
All reactions