[FR]: Non-setting statuses need to be accounted for

[cstelmach]

Feature Category

Views (Calendar, Kanban, Agenda, Task List, Notes)

Problem Statement

• Any change to the status property will create a new kanban list with the value, if it doesn't exist yet (as seen in the image example with the note fdsafadsfsdfd, where the status nonsettingstatus has not been defined once in the settings.
• You are able to add items to lists that are not defined in the status settings (e.g. I could still use the open and in-progress lists and the items would show there, if I manually enter the values.
• The non-disappearing statuses of past items have already been mentioned in [Bug]: Kanban view showing additional statuses after renaming an existing one #258

Proposed Solution

For the statuses which are not in the settings there are two obvious options (or a settings toggle for choosing one or them):

1. Show those non-settings statuses.

I would maybe add a bit of a darker shading or something that would instinctively show that these are non-standard. In some cases they might be errors that users want to detect, in others it might be part of the workflow.

2. Hide all of the statuses (and their notes) that are not defined in the task settings completely.

One thing that can be assumed is that any task note with a non-standard status has not been created by the TaskNotes app, or has an error (like by changing the status settings), so generally conditions where a user might not want to see them.
Maybe in the future there will be a functionality where other hidden notes are stored/shown (e.g. archived notes when you have >100 completed ones and don't want to see them.), which would allow you to also hide/show them there.

Use Case Examples

Use case for 1.:

Different Task plugin or something. Notes are created with a foreign status. You know that it is not created by TaskNotes but external. But you still have the option via Right Click for example to then put them into your TaskNotes flow, even if an external application has provided you with the first note. (although you can easily add the respective status to your settings, but who knows).
In the case of 1. you want those notes to at some point be integrated into your flow.

Use case for 2.:

Same thing as the case for 1., but you don't want the notes to be integrated into your flow. You don't want to see them or at least not to swarm your Kanban board.

Priority/Impact

None

Additional Context

I discovered this bug/hidden feature when encountering #258 . I think it might be useful somehow, or not. But it for sure needs to be accounted for.

Thank you.

[digitaldoctors]

ive had this problem as well.

I worked really hard thinking I could prevent manual entry in the YAML properties.
I was able to make clickable menus with MetaData Menu, but it STILL allowed manual entry.

I want 5 status options and Obsidian needs to make it impossible to enter anything but those 5.

Seems like it's impossible.

And Bases makes it worse ! You can't restrict anything in bases.

I've resorted to making Meta Bind buttons that update YAML but live in the Note section. I am going to encourage my staff to avoid YAML wherever possible.

#246

[callumalpass]

Hi @digitaldoctors . I wonder if you might find the "Quick actions for current task" command helpful? It is available when you have a tasknote open in the editor. It forces you to choose from the statuses that are defined in the settings.

[callumalpass]

@cstelmach , thanks for raising this. I think--but I'm not 100% sure--that I will make the status boards defined by the settings.

[callumalpass]

Thank you for reporting this. This should be resolved in release 4.8.0, so I am going to close this issue now.