Musa

Explain the problem as you see it

I have a node query that return supertags that inherit from a particular supertag. The purpose is to quickly pivot into each of those supertag's view that I've designed. However, when you do this, Tana doesn't behave as you expect. It instead turns each of the supertags into a new, empty node instantiated with those supertags.

Why is this a problem for you?

I've spent time designing the supertag pages with appropriate columns but it can't be visualized through a navigational view like sidebar or tabs. When you do it, the supertags essentially turn into an empty node.

Suggest a solution

When navigating to the supertag nodes via Tana's navigation views like sidebar and tabs, show the Supertag's home page.

Explain the problem as you see it

Sometimes I close the panel and would like to re-open it with a simple shortcut. However, this is not possible, as there's no command to re-open recently closed tab.

Why is this a problem for you?

I can't easily re-open a panel.

Suggest a solution

Have a command you can assign to a shortcut or provide a functionality of out of the box tied to a shortcut people have muscle memory for (CMD + SHIFT + T) to re-open previously closed panels in the same panel location they previously were. There should be a buffer so that more than one panel can be restored.

Explain the problem as you see it

I use Pomodone, but I would like for it to be integrated with Pomodone for seamless tracking. It's one of the leading Pomodoro applications with a great ecosystem of integration partners.

Why is this a problem for you?

I have to create tasks manually in Pomodone and track them in two different places. It would be good to push them to Pomodone and have them synchronously tracked.

Suggest a solution

Work with the Pomodone team to integrate natively to push projects/tasks to Pomodone.

Explain the problem as you see it

When you click into a field of type: instance and the drop-down pops up, completed items are showing up in the result with the same priority or higher than non-completed items and it's not identifiable that it's complete.

Why is this a problem for you?

I've found this to be a problem in GTD systems. One of the topics I always assign my to-dos is a Related Project field. However, it basically searches by hits and doesn't weigh any factor toward the item being completed. I have several projects that have the same keywords, and it makes it confusing as to which one to pick.

Suggest a solution

1. Add weight to the results so that if the fuzzy search returns two supertag instances, one with a check and another with an unchecked mapping, then bring the unchecked to the top.
2. Add a cross-out and dim the font if the supertag instance returned has a status that's mapped to complete.

Explain the problem as you see it

As you start adding commands to your supertags, the actions you add are taking up lots of real estate.

Why is this a problem for you?

Some of my nodes have 5+ commands attached and seeing them repeated in a list of 50+ items, is very cluttering, distracting, and not appealing.

Suggest a solution

Something like this community fix, but that actually works ;-)

Explain the problem as you see it

When defining supertag templates in Tana, currently, users must create a node with child nodes visualizable as Tabs, a common practice in dashboard creation (i.e., setting >Attribute == PARENT).

This method, however, contributes to a problematic 'nesting hell' phenomenon in the existing Tana UI/UX flow. The issue manifests particularly with tags like #day and #person, where opening the node is required to see related tasks, projects, or notes tied to the day or individual.

Why is this a problem for you?

This node-based structure produces an excessive and often frustrating level of nesting in Tana's UX/UI. Directly anchoring nodes to generated node titles (e.g., "Today, Tue, Aug 01") would offer a more intuitive, dashboard-like feel. Such a setup would present the main elements for review immediately upon opening, reducing the need for additional layers of navigation. Regardless of the ability to recall which nodes should be open, anchoring nodes directly under the node title would greatly enhance UX by creating a more natural, entity-specific dashboard.

Suggest a solution

Permit users to establish a "view as" setting on chosen nodes within the supertag template.