Add TasksDates for custom statuses

[timoerlemans]

I was looking to create a query in my daily note that lists all the tasks that I worked on that day but didn't finish.
I've tried the following query

(status.type is IN_PROGRESS) OR (done after 2024-03-19)
happens 2024-03-19

Which works if you have either a Start, Scheduled or Due date, but this doesn't make the query reliable, as these dates are not required and also not set automatically when changing the status to IN_PROGRESS.

I also wanted to create a query that lists all the tasks that I STARTED on that day, but that simply doesn't seem to be possible, because that date is not tracked and not queryable.

I couldn't find a TasksDate in the documentation for Started or something like that, then it dawned on me that IN_PROGRESS status is a custom status.

So I was wondering if it would be possible to track dates of custom statuses in the same way as Done, Canceled, Created?
I couldn't find any discussion, issue or pull request that relates to this.

I'd suggest to make this as generic as possible, as you can't possibly no what custom statuses a user has, and which statuses he wants to have tracked. Like a property in the Tasks class with the name Custom_Status with an object that lists all available custom statuses and their dates.

It might be a challenge to choose a emoji for these custom statuses, though.

I was already looking at the code if I could do something myself. I'm quite proficient at JS/TypeScript but I don't know anything about creating Obsidian plugins. I also realise this is not a simple feature to add so I wanted to start a discussion about it first.

Do you think this is feasible? What would be the best way to do this so it works for every status?

[claremacrae]

Thank you for using the Tasks plugin, and for taking the time to make a suggestion.

Background

As per the title of this section - Ideas: Any New Feature Requests go in Issues please, we don't track feature requests in Discussions any more.

(Bugs have always been tracked in Issues.)

Here are some of the reasons why the need for this change:

• Plan switch to recording new feature requests in Issues instead of Discussions/Ideas #1168

I had to leave Ideas Discussions open to allow people to comment on existing ideas, and so we could track their votes, so I renamed the section to try to point people to Ideas instead for new reports.

Request

So I would be grateful if you would go to Issues, click New Issue and submit your request there...

I'm going to close this now, and look forward to receiving your report in Issues.

Thanks again.

[timoerlemans]

Sorry for posting it in the wrong place. I have created an issue for it.
#2720