Denis Bogdanas

Explain the problem as you see it

Right now the query clause NOT: PARENT DESCENDANTS WITH REFS does not work. Computation never finishes.

Why is this a problem for you?

It is useful if I have a bunch of queries for a certain #tag with various constraints, all under one node, and I want to find all #tag that was not covered by those queries. Incredibly useful when I'm classifying instances of a tag and want to find what is left out.

Suggest a solution

Such a query is an instance of Russell Paradox. So understandably it cannot be computed. But it is easy to get around it. Queries with constraints referring to parent/grandparent should simply not search inside themselves.

Explain the problem as you see it

Suppose we have:
Cat 1

• task 1
• task 2#priority
  Cat 2
• task 3
• task 4 #priority

Query: all with #priority

I want tasks to be grouped by category

Why is this a problem for you?

Sure we can achieve this result with more structure, by having #task with field category, but often we want a simple grouping without too much setup and refactoring for existing notes.

Suggest a solution

Add parent/grandparent to system fields available in group by clause of searches.

Explain the problem as you see it

The main way I use AI chat is to research various topics on the web, which is currently not possible in Tana.

Why is this a problem for you?

I would much prefer to keep those chats in Tana where they can be easily searched and organized, rather than having them in ChatGPT and copy-pasting snippets that I want to keep.

Suggest a solution

Full integration with AI APIs, similarly to how it's done in Poe for example.

I imagine this would lead to some complications. AI chats can quickly turn very large and pollute searches within Tana. A fix for this would be the ability to tune search options and enable/disable search in chats.

Explain the problem as you see it

It would be very helpful to navigate between nodes using only the keyboard. Just like Today node can be opened with Ctrl+Shift+D.

Why is this a problem for you?

This would make navigation much more comfortable between frequently used nodes, like tasks and daily journal. Especially when proper mouse is not available.

Suggest a solution

For this, all we need is the ability to assign shortcut keys to "search and open node" action.

This is straightforward to implement in the UI. In the search view, we need the ability to record a shortcut via Ctrl+Shift+K, like in the command view.