Sorting Of Groups Themselve

[702573N]

My Setup And Problem

Based on my personal needs, I have created a categorized overview of all my tasks. Using the Obsidian Tabs plugin (https://github.com/xhuajin/obsidian-tabs) by @xhuajin, I can switch between the categories Timeline, Tags (🏷️ Tag), Projects (🔗 Project), Mentions (👤 Person, 👥 Group, 🏢 Company) and Comments (subitems for each task starting with datestamp). In my system, mentions and projects are [[backlinks]] within the task description. The tasks are grouped accordingly in each tab category. Within each individual group, the tasks contained therein are sorted by happens date. What I am still missing, however, is a sorting of the groups themselves. I would like to sort all groups that have at least one task with a happens date to the top of the list so that I can focus on them more quickly. My tasks are also highlighted using custom CSS according to a user-defined color scheme (mint = undated, yellow = in progress, orange = today, red = overdue, green = done).

Does anyone have any idea whether this sorting I want to do using group by function can be implemented?

The simplest solution to put the tasks with happens date at the beginning is to put the happens date %%{{happens}}%% in front of the group name. However, this means that these groups may exist twice. One group for scheduled tasks at the beginning of the list and another group with the same name for all tasks without a happens date. This makes this solution unusable for me.

Failed Solution Approach 1

group by function task.description.match(/(👤|👥|🏢)\W[a-zA-ZäöüÄÖÜß]+/g).map((desc)=> "%%"+task.happens.moment+"%%<div class='taskHead'>" + desc.split('/')[0] + "</div>")

I have also already tried to write each group within the function in an object with a specific sort key. For each task, the system then checks whether such a group is already contained in the object and which sort key it has. I can then put this sort key %%{{sortKey}}%% in front of the group name to ensure sorting according to this. However, this procedure only works if the first task of the corresponding group already has a happens date. However, if the first task of a new group has no happens date, the incorrect sort-key is written to the object and cannot be recursively overwritten for all previous tasks.

Failed Solution Approach 2

group by function { \
    const mentions = task.description.match(/(👤|👥|🏢)\W[a-zA-ZäöüÄÖÜß]+/g); \
    const happens = task.happens.moment; \
    let alreadyHandledMentions = {}; \
    \
    return mentions ? mentions.map(mention => { \
        if (alreadyHandledMentions[mention]) { \
            return alreadyHandledMentions[mention] + mention; \
        } else { \
            const orderPrefix = happens ? '0' : '1'; \
            alreadyHandledMentions[mention] = orderPrefix; \
            return orderPrefix + mention; \
        } \
    }) : '%%1%%No Mention'; \
}

It would be really great if anyone here had a helpful idea. I hope you do too.

Screenshot

Sample Tasks

- [ ] Test before final Release [[🔗 work]] [[🏢 Apple]] [[👤 Tim]] #progress 🛫 2024-04-28 📅 2024-12-31
- [ ] Automation-Project [[🔗 work]] [[👤 Tim]] #progress 🛫 2024-02-01
- [ ] Ask for help on GitHub #todo [[🔗 work]] [[👤 claremacrae]]
- [ ] Paint Mona Lisa #backlog [[🔗 home]] [[👤 Jeff]]

Files

Tasklist CSS-Snippet.txt
Tasklist.txt

• GitHub doesn't support uploading *.md files, so you have to rename the file-extension

[claremacrae]

Please look at the Custom Grouping docs page.

There is a section explaining using hidden text in markdown comments to control the sorting.

That is what you need to do.

[702573N]

This is what I have done (and written above), but doesn't help in this case. Any solution ideas?

[702573N]

Of course, I have looked at the document page for custom grouping before and work with it in my solution steps. This is of course the right way to accomplish sorting. But it's not the solution to my actual problem because it can lead to duplicate groups, which I don't want. The main problem here is not adding a sort key with hidden text, but retrieving information about other tasks while another task within the group function is being processed.

[claremacrae]

This is of course the right way to accomplish sorting. But it's not the solution to my actual problem because it can lead to duplicate groups, which I don't want.

Honestly, I don't have time to read through long requests any more. To deal requests this verbose thoroughly takes an hour or more.

Specific questions are easier to answer.

The main problem here is not adding a sort key with hidden text, but retrieving information about other tasks while another task within the group function is being processed.

See https://publish.obsidian.md/tasks/Scripting/Query+Properties#Values+for+Query+Search+Properties

query.allTasks

[702573N]

Thank you very much for the hint with tasks.queryAll. I was actually unaware of this function and seem to have overlooked it in the documentation. After a few attempts I was able to create a working script. The result is now exactly what I wanted.

I first filter out all mentions that come from tasks that have a happens date using tasks.queryAll. In the group by function procedure, the mentions of each task are then matched with my prioMentions array.

For some reason, neither the check via includes nor via some works with my prioMentions array. Only if I convert the array into a string using join and then check it using indexOf() does work. It's just a blemish, but at least it works.

Thank you for your time.

group by function { \
	var regEx = /(👤|👥|🏢)\W[a-zA-ZäöüÄÖÜß]+/g; \
    const mentions = task.description.match(regEx); \
    let prioMentions = query.allTasks.filter(task => task.description.match(regEx) && task.happens.moment && !task.done.moment).flatMap(task => task.description.match(regEx) ); \
    return mentions ? mentions.map(mention => { \
        if (prioMentions.join('').indexOf(mention) > -1) { \
            return '%%0%%' + mention; \
        } else { \
            return '%%1%%' + mention; \
        } \
    }) : ''; \
}

[claremacrae]

Thank you for reporting back with the solution, to help others.