jamiebrynes7
feat: Add default task properties to new Todoist Task
Is your feature request related to a problem? Please describe. I am constantly adding tasks from Obsidian that I like to explicitly add labels to that are "Obsidian Task" or something equivalent to that. I also only have a few projects that I would be adding a task to, so it would be nice to be able to set a default project to not have to always add the project and label manually.
Describe the solution you'd like Set "Add Task" item that can have a default Tasks template for labels, projects.
Describe alternatives you've considered Manually doing through so the user interface or trying to remember what symbol triggers what thing in Todoist.
Additional context Add any other context or screenshots about the feature request here.
My uncooked shower thought (I have been wanting this since discovering this plugin (and Obsidian) last week):
The add task button should possibly use whatever is in filter in the block definition.
But as I said this was an uncooked idea. I realized while typing this that it has some flaws. Namely it would work for simple filters like filter: "#some-project @some-label", but adding more complex queries like "today | overdue" would not work, so additional parsing would need to be done. Maybe it could just parse out tokens that start with #, @, and possibly also due date or whatever else might make sense.
I'm not sure if it’s appropriate to post about another plugin, but the following plugin I developed can identify task properties of Dataview and Tasks formats.
https://github.com/wenlzhang/obsidian-todoist-context-bridge
I'd be equally fine with adding a new property to the YAML that just takes the same syntax todoist uses when writing a query and prepends it to any new task by default. This could use the Sync API's Quick Add functionality which supports parsing things the same way the native desktop and mobile applications do, and shouldn't be very difficult to plumb in. That would also allow arbitrary text if desired.
Something like:
filter: "##Household & /Recurring"
quickadd: "#Household /Recurring today @obsidian Arbitrary Text"
I don't think it's critical that these bits be interpreted by the plugin UI. I'd be fine with the existence of a quickadd key overriding whatever is in the UI. Optionally, a similar notice to the user could be displayed below the "A link to this page will be appended to the task name" text informing the user that their settings will be overridden by the prepended parameters if specified. This minimizes the amount of work the plugin itself would actually need to do in interpreting the prepended string.
