Add created date as a property of the task based off the file?

[sytone]

Was looking to sort by created date but there is not a property for this. The Created or Last Modified date of the note it is located in could be a good proxy. Ideally there would be a property on the task that tracks this like scheduled, due, etc.

Thoughts?

Could have it use the page created/modified if not on the task explicitly so people that make tasks in their daily notes would be able to use this without adding the date to the task as a property and if you wanted to you could add it as a override. Trying to summarize the other discussions on this as there have been a few different ones. The Design idea is below to try and bring it all together.

• Feature request: Query tasks based on creation date #98
• Support file.ctime/ mtime when querying tasks #93
• Support sorting tasks based on file creation/modification date #405
• Allow filtering by file.day #491
• Filter tasks by the date when they were created #486
• Creation date filter #575

#98 has a implementation example, it add another tag to the task if needed. This is similar to #486 which just has a string in the description. #93 and #405 and #491.

Design Proposal

• Add a new optional property to the task like ✏️ {DATE}.
• Add this by default to all new tasks.
  • Option a user has to enable in settings, disabled by default.
• If this does not exist fall back to the page creation or modified date that the task lives in.
  • User must pick one in settings to use by default (Created or modified)
• The edit UI adds the new field which is auto filed with the current day to make input simpler.
  • This would only be shown/added if user has enabled add by default to all tasks in settings.
• Add a new filter created (before|after|on|between) <date> <date>
• Add a new sort sort by created
• Add new layout option hide created date

[claremacrae]

See Discussion #405
"Support sorting tasks based on file creation/modification date"

[sytone]

You responded while I was updating the main post 😄

[panahi]

Also interested in this, to make my daily note queries more valuable. Maybe a setting that will automatically apply a tag like YYYYMMDD when a task is created (I have mine set to manage all markdown tasks)?

[sytone]

the obsidian-tasks-x fork has this as a property, it also allows you to query using the page details that the task was created on.

[claremacrae]

The new optional created field was was released, in Tasks 2.0.0.

Example:
- [ ] take out the trash ➕ 2021-04-09

Docs:

• Adding the created field
  • please read, to see how to add the created date automatically, and known limitations
• Searching the created field

[sascha-wi]

Both of these solutions are cumbersome, is there no better way? For example if I am creating a daily note and it has a creation date, that all tasks created on that file get that creation date added?

[sascha-wi]

Esp. even trying the "Tasks: Create or edit task" command, its totally reliant on where your cursor is on the note. Why? What workflow is using that process of typing ctrl + p and "create task" AFTER they already described what the task is about? Its much easier to just add to your preexisting list of tasks - [ ] taskname here.
Maybe I am not seeing the light here...

[claremacrae]

@sascha-wi. This project is maintained by volunteers in our spare time. There is always more to do than time available.

Please try to keep your comments kinder in future.

There are indeed other options.
For example, you can change your daily note templates to generate the created date on any tasks the template adds.
Or you can change your searches to select tasks based on the file name of the daily note.

[claremacrae]

In view of this size of the backlog for this project, and the demotivating effect of a very long backlog on volunteer energy levels, I'm going through a continual process of reviewing tasks for things that are one or more of the following:

• unlikely to be realistically achievable, from the design of the current code, and the planned future refactorings
• not sufficiently high priority to a broad community of users, based on the feedback I receive from a variety of sources
• do not fit the core purpose of the Tasks plugin
• are better covered by a different plugin - to share the development and maintenance effort

So I'm marking this one as 'not planned'. This doesn't mean 'won't fix' - it means not likely to be done in the foreseeable future.

[erauner12]

All good! Thank you for the continued effort!