Maciej Smoła

Explain the problem as you see it

There is no way to reference a node that is more than GRANDPARENT level above search node.

Why is this a problem for you?

I have structured content with multiple relationships between them like (tags are only examples):
/- Level 1 #book
/-- Level 2 #chapter
/--- Level 3 #topic
/---- Level 4 #paragraph
/----- Level 5 #sentence

I have tasks for node from one of the levels (e.g. fixes for sentence or improvements on topic). Then I have searches in each level's supertag template. Each level deeper supertag has field of level up supertag with "Part of" relationship.

I would like to have a search connected to each supertag templates to find all tasks connected to the current level – that is to the level itself and to all of the levels deeper.

So at Level 5 sentence I would get only tasks with Level 5 link in its fields but at Level 3 search I would get all tasks related to whole topic, alongside with paragraph (Level 4) and sentence (Level 5) tasks.

Suggest a solution

Make a search operator with a more flexible way to point at specific ancestor node level:

• PARENT_1 (= PARENT)
• PARENT_2 (= GRANDPARENT)
• PARENT_3 (=GREATGRANDPARENT)
• and so on, without limit to the number.

Explain the problem as you see it

One of Tana's features is task management. However there is no way to sync it with any of existing todo apps.

Why is this a problem for you?

I would like to have a way to manage tasks in Todoist (which is also used by my wife for shared projects like Home Tasks) while being able to integrate it with other stuff in Tana. If Tana would ever incorporate full task management workflow I would be happy to switch completely (with mobile app, recurring tasks and timed and persistent notifications).

Todoist integration is a bit more special because of multiple Todoist integrations. That way, Tana could integrate with other services with Todoist as a middleman (like tasks in calendar apps like Fantastical).

Suggest a solution

Two-way sync with Todoist

Explain the problem as you see it

There is no integration between iCloud calendar and Tana. Only way to do it is via manual input of an event in Tana.

Why is this a problem for you?

I would like to work around nodes which are connected to events (and tasks) from other apps. It would allow me to make better meeting notes and better planning around specific events. With addition of tasks integration and calendar view, Tana could become a great, customizable daily planner with huge note taking possibilities.

Suggest a solution

Two-way sync with iCloud calendar.

• New event in calendar creates a node in Tana, with specific supertag and fields values. It is then placed on the timeline of a calendar view (like in Routine app).
• New node in Tana matching specific criteria creates an event in specific calendar, time etc.
• Any changes in Tana or Calendar got synced in a two-way manner.

Explain the problem as you see it

There is a way to type a string, search for it and then create it via the same popup – but only if using "@" search. It is not possible to do this via search from the top bar.

Why is this a problem for you?

There is no way to create a node via search from top bar, which could be helpful especially if the results came up empty.

Suggest a solution

Option to create a node in Day Node or Library via search from top bar.

Explain the problem as you see it

There is no way to merge fields.

Why is this a problem for you?

I have several fields which I would like to merge and I cannot do it quickly.

Suggest a solution

A way to merge fields.

Explain the problem as you see it

Having "Build title from fields" append text at the end of a node is not always optimal.

Why is this a problem for you?

I would like to have fields information gathered under the node and at the beggining of it to be able to quickly compare different values.

Suggest a solution

Improved verision but working everywhere feature which is partly there - in search results, after enabling fields from "Display":

Explain the problem as you see it

We can use "Build title from fields" function with

${name} ${field 1} ${field 2}

which makes editable node's name with field 1 & 2 appended at the end.

However it is not posiible to retain editability of node's name, if the structure doesn't have ${name} at the start, e.g. in case like this:

${field 1} ${field 2} ${name}

Why is this a problem for you?

I would like to prepend node title with some status emojis which is better than appending them at the end but I cannot do that because nodes name become uneditable then.

Suggest a solution

More robust "Build from fields" function with editable ${name} regardless of its position in <Build title from fields> formula.

Explain the problem as you see it

I have a lot of stuff in Airtable which I would like to refer to and use in Tana.

Example:
Around 1000 images with metadata in fields sits in my Airtable. It would be a game-changer for me, if I could link to it with Tana and work around each record, create tasks based on them etc.

Why is this a problem for you?

I need to jump back and forth between two apps, link them manually together via standard URLs and I cannot check Airtable data right in Tana.

Suggest a solution

1/ Best: Two-way Airtable integration with fields in Tana = fields in Airtable.
2/ At least: Import Airtable database view to tana

Explain the problem you see

In some cases, version tracking is a must. Now the only way is duplicating the node and moving it somewhere else – under the duplicated node or other "Older versions" node.

Why is this a problem?

It is causing structure to be more messy than necessary. In addition, every user could have a time where he changed a node and would like to change it back to it's previous state.

Suggest a solution

Hovering on the node or using command line prompt would allow to enter the history view of the node with dates of changes.

Explain the problem you see

There is no way to use inline referencing due to limitations of aliases.

Why is this a problem?

• Longer nodes can be shortened only to few symbols like "*"
• Absence of different word conjugations where they are needed makes sentences look bad

Suggest a solution

• Ability to link any selected plain text to any other node
• Ability to edit an inline reference text while still maintaining its linking

Explain the problem you see

There is no way to see if a hidden field is hidden because:

• it is empty or filled with "Always Hide" option selected
• it is empty with "Hide when empty" option selected
• it is filled with "Hide when filled" option selected
• etc...

Why is this a problem?

Hidden fields always look the same - with “+” sign at the start, indicating in some way that they are all empty (when some of them can be e.g. filled with "Always Hide").

Suggest a solution

Different ways to show hidden fields based on whether they are empty, default or filled.