Unfortunately, if I specify a project name, this line is created as a task instead of (what I expect) that any indented task is created within the specified project. For example I have this draft:
Test project:
- Do stuff
- Do more stuff
This is created in my Inbox as a first level task of âTest projectâ with 2 sub tasks. My expectation was that I would get 2 first level tasks created in the project, or have 2 tasks in the Inbox, with the project as their attribute.
Is this way of specifying projects supported? Am I doing something wrong?
Thanks for pointing this out. I had already figured this out, too. The thing is: the taskpaper specs on the support page refer to project items conforming to the official specs. But pasting a line ending in : and a newline does not do anything.
So Iâm still curious if and how lines with Project names are supported when pasting.
What do you mean by that? If you use the syntax I posted, it creates a top level project. Perhaps Iâm missing somethingâŚCould you give more details?
A project is a line that isnât a task and ends with a colon (â:â), or a colon (â:\nâ) followed by a newline. Tags can exist after the colon, but if any non-tag text is present, then it wonât be recognized as a project.
My expectation is, that if I paste a draft with this syntax, al tasks that are in this draftâs project will get this project in OF.
This is default TP behavior and allows one to add tasks to different projects from one draft.
This lets you create one single task whereas the paste function allows for a batch/hierarchy.
Well, actually there is. By design, completed items can be moved to an Archive: section in the file and get that tag with the original projectâs name. Perhaps this tag could/should be supported by OF, too.
Itâs going to create a new project in the location specified by the target optional parameter. If itâs not provided, it will paste it in the inbox.
This syntax allow for the creation of new projects/action groups/tasks.
add command creates one task at a time. You probably know this, but you could use a Workflow Repeat action to create many tasks (ie. in a specific project) with this command. Of course, it would create a flat list, not allowing hierarchy.
I think there is a reason to not support @project tag. If a user tries to paste TP text with a this tag, what do you expect to happen?
Pasting TP text into OF allows for creation of projects/action groups/tasks via URL Schemes, currently.
So, if the target is a folder, it will create a new project there?
I would expect that specific task to be added to the project concerned if it already exists or the Inbox if the project does not yet exist. Does this make sense?