Differentiate tags from description

[laawn]

Use case:
I have "-s" as my primary status tag with sub-tavs delineating the status of a task (backlog, next, etc). I can differentiate between the tags easily with filters but am unable to sort correctly. Sorting by description sorts the name of the task, not the tag.

By separating tags from description entirely, I believe it would fix this problem and making filtering tags more intuitive.

[therden]

Hello @laawn.

It sounds as though you use a relatively small, standardized set of these "-s" tags.

If that's correct, then you can control of the order in which items with those tags are presented by creating a series of Tasks queries, each of which filters for a different "-s" tag, like so:

```tasks
not done
description includes -s-next
hide task count
```
```tasks
not done
description includes -s-backlog
hide task count
```

With the above approach, you can present the matching tasks in alphabetical order, reverse alphabetical order, or any other order you desire.

[laawn]

I understand that approach.

I guess my primary goal was to be able to have master lists on my dashboard (i.e. Due Today, Next Actions, Backlog) etc, which would include all next actions, backlog, etc but sorted by role/context.

I'd like to be able to do something like this:

not done
description includes #-s/next
sort by tag

Ideally, it would list all of my next actions for all roles but sort all next actions by role/context. Example:

[ ] To do 1 #-s/next #-r/father
[ ] To do 2 #-s/next #-r/father
[ ] To do 1 #-s/next #-r/homeowner
[ ] To do 2 #-s/next #-r/homeowner
[ ] To do 1 #-s/next #-r/work
[ ] To do 2 #-s/next #-r/work

I realize I could do a separate one for each role/context but that would create a massively messy dashboard that ultimately wouldn't serve the purpose. My current approach is to only list Today, Tomorrow, Later, Waiting4 on my dashboard; and then have a heading for Next/Backlog at the bottom with a list of links to the roles/contexts.

[therden]

I think I see what you're aiming for. I haven't used it much, but I think that you could accomplish your aims using the Dataview plugin -- if you'd be willing to transform the tags that you want to select and sort on into the type of inline field:: value pairs that it supports.

[therden]

@laawn I still feel that you could get the presentation that you want using a series of queries. Although the one-time set up (and occasional later tweaks as your add role/context tags) may be a bit laborious, I can't see why the Preview of your dashboard would be "massively messy".

For example, given the following tasks spread across various notes in your vault:

- [ ] a task due today #-r/work   📅 2022-02-11
- [ ] a task due today #-r/homeowner   📅 2022-02-11
- [ ] To do whenever 1 #-s/next #-r/work  
- [ ] To do whenever 1 #-s/next #-r/homeowner  
- [ ] a task due yesterday #-r/work  📅 2022-02-10
- [ ] a task due tomorrow #-r/father   📅 2022-02-12
- [ ] To do whenever 2 #-s/next #-r/work
- [ ] a task due yesterday #-r/father  📅 2022-02-10
- [ ] a task due yesterday #-r/homeowner  📅 2022-02-10
- [ ] a task due tomorrow #-r/homeowner   📅 2022-02-12
- [ ] To do whenever 2 #-s/next #-r/homeowner  
- [ ] a task due today #-r/father   📅 2022-02-11
- [ ] To do whenever 2 #-s/next #-r/father  
- [ ] a task due tomorrow #-r/work   📅 2022-02-12
- [ ] To do whenever 1 #-s/next #-r/father  

including the following queries in your Dashboard

###Due today

```tasks
due today
not done
description includes #-r/father
hide task count
```
```tasks
due today
not done
description includes #-r/homeowner
hide task count
```
```tasks
due today
not done
description includes #-r/work
hide task count
```

###Next Actions

```tasks
no due date
not done
description includes #-s/next
description includes #-r/father
hide task count
```
```tasks
no due date
not done
description includes #-s/next
description includes #-r/homeowner
hide task count
```
```tasks
no due date
not done
description includes #-s/next
description includes #-r/work
hide task count
```

will display your Due Today and Next tasks as if they were sorted by #-r tag:

[schemar]

Hey @laawn, thank you for the idea. I totally get your rationale. It's just that I don't think I have the time to implement and maintain a separation of description and tags.

[laawn]

@schemar @therden I'll settle for tag suggestion in the Tasks modal =)

[therden]

Hi @laawn,

When constructing a Tasks query, once you enter a single # character, Obsidian automatically provides a list of tags which are used in the vault -- and with each additional character you type, the list of suggested tags narrows to match.

Since it seems unlikely that you're asking for a feature that already exists, can you please clarify what you mean by "tag suggestion in the Tasks modal"? Thanks in advance!

[laawn]

Hi @laawn,

When constructing a Tasks query, once you enter a single # character, Obsidian automatically provides a list of tags which are used in the vault -- and with each additional character you type, the list of suggested tags narrows to match.

Since it seems unlikely that you're asking for a feature that already exists, can you please clarify what you mean by "tag suggestion in the Tasks modal"? Thanks in advance!

In the modal pop-up when editing a task, Obsidian does not provide the tag suggestions. I think there was already a thread about this in which @schemar replied. I'm just adding my vote. Thanks!

[therden]

I understand now-- you want tag suggestions in the Create or edit Task dialog. Thank you for clarifying, @laawn.

On another note: the formatting and quote of my message your post from 10 days ago (below), make it hard to find and read your reply.
If you're able and willing to take a minute to edit and make it more legible, then just click the 3 dots at the upper right of your post and select Edit. Thanks again!

[laawn]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:"Segoe UI Emoji"; panose-1:2 11 5 2 4 2 4 2 2 3;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;} h3 {mso-style-priority:9; mso-style-link:"Heading 3 Char"; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:13.5pt; font-family:"Calibri",sans-serif; font-weight:bold;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} code {mso-style-priority:99; font-family:"Courier New";} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; font-size:10.0pt; font-family:"Courier New";} span.Heading3Char {mso-style-name:"Heading 3 Char"; mso-style-priority:9; mso-style-link:"Heading 3"; font-family:"Calibri",sans-serif; font-weight:bold;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:"Courier New";} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} -->Fair. I guess my intent was have a query that I could change in-the-moment based on the context of the environment I’m in, but I don’t see why your method wouldn’t work well. I had an issue the first 2 months after Live Preview came out for Insiders, where notes with large queries (especially Tasks) would cause intermittent lag while typing. This seems to have mostly resolved within the last 4-6 weeks, so I think that method would work well. I wish I knew how to code better, so I could help you =\   V/R Nate From: therdenSent: Friday, February 11, 2022 12:31 PMTo: schemar/obsidian-tasksCc: Nate; MentionSubject: Re: [schemar/obsidian-tasks] Differentiate tags from description (Discussion ***@***.*** I still feel that you could get the presentation that you want using a series of queries. Although the one-time set up (and occasional later tweaks as your add role/context tags) may be a bit laborious, I can't see why the Preview of your dashboard would be "massively messy".For example, given the following tasks spread across various notes in your vault:- [ ] a task due today #-r/work   📅 2022-02-11 - [ ] a task due today #-r/homeowner   📅 2022-02-11 - [ ] To do whenever 1 #-s/next #-r/work   - [ ] To do whenever 1 #-s/next #-r/homeowner   - [ ] a task due yesterday #-r/work  📅 2022-02-10 - [ ] a task due tomorrow #-r/father   📅 2022-02-12 - [ ] To do whenever 2 #-s/next #-r/work - [ ] a task due yesterday #-r/father  📅 2022-02-10 - [ ] a task due yesterday #-r/homeowner  📅 2022-02-10 - [ ] a task due tomorrow #-r/homeowner   📅 2022-02-12 - [ ] To do whenever 2 #-s/next #-r/homeowner   - [ ] a task due today #-r/father   📅 2022-02-11 - [ ] To do whenever 2 #-s/next #-r/father   - [ ] a task due tomorrow #-r/work   📅 2022-02-12 - [ ] To do whenever 1 #-s/next #-r/father   including the following queries in your Dashboard###Due today```tasksdue todaynot donedescription includes #-r/fatherhide task count``````tasksdue todaynot donedescription includes #-r/homeownerhide task count``````tasksdue todaynot donedescription includes #-r/workhide task count```###Next Actions```tasksno due datenot donedescription includes #-s/nextdescription includes #-r/fatherhide task count``````tasksno due datenot donedescription includes #-s/nextdescription includes #-r/homeownerhide task count``````tasksno due datenot donedescription includes #-s/nextdescription includes #-r/workhide task count```will display your Due Today and Next tasks as if they were sorted by #-r tag:—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***> 

[claremacrae]

Hi, just to let you know that recently the ability to filter, sort and group by tags have all been released.