Keep original order of tasks in query results when sorting by path

[giuthas]

Hi all,

Would it be possible to keep order tasks appeared in a given file in query results when sorting by path?

What I mean is something like this:

Some_task_file:

• task1
• task2
• task3

Some_other_task_file:

• taskA
• other task

Query in a third file that matches all of the above and with 'sort by path' would ideally return

• taskA
• other task
• task1
• task2
• task3

instead of the random order we now get.

Cheers!

[schemar]

Thank you for the feedback @giuthas! This is already tracked in #383 and #439. Order should stay the same as in each file. I didn't have the time yet to look into it.

[spinda]

Would it help to have "location within the file" as a sortable properly? Kinda like how you can sort by heading now, but with the character index at which the task appears in its source file.

[FloMiLe]

It would be nice to be able to complete disable sorting of queried tasks, such that they appear in the same order as in the file they were found in, and contrary to how it is described here: https://publish.obsidian.md/tasks/Queries/Sorting.

The reason I am saying this is, that some of my tasks have a due date, and some don't. And yet, I would like to have them displayed in the order I put them in in the original file.

Thanks for considering!

[claremacrae]

I'm tracking feature requests in Issues now.

Whilst I'm not generally moving earlier feature requests from Discussions to Issues, we do have an Issue for this already....

• Add instruction to sort tasks by line number in the file, in order to preserve the original order #2213

... and keeping duplicates just takes up time.

So I'll close this one - please 👍 that other one. Thanks.

[FloMiLe]

Thanks for pointing this out, and sorry for issuing a redundant request!

[claremacrae]

Thanks but please don't worry @FloMiLe - there are so many similar requests in Discussions it's hard to spot them all, and keep track.

Also, when this request was made in Discussions, back in January 2022, it was in the right place at the time...