Maciej Smoła

Explain the problem as you see it

We have several useful fields/parameters like:

${cdate} and ${ctime} - Created date and time
${mdate} and ${mtime} - Modified date and time
${sys:description} - Description field
${sys:createdAt} - Time of creation
${sys:lastModifiedAt} - Time of last edit
${sys:lastModifiedBy} - User who last edited the node
${sys:modifiedBy} - All users who ever created/modified the node
${sys:owner} - Parent node
${sys:dateFromDayNode} - The day node this node belongs to (Calendar date system field)
${sys:doneTime} - Date and time this node was marked done

A new one like ${sys:convertedToTaskTime} and ${sys:taggedAs{{CUSTOMTAGNAME}}Time} would be useful to show when a node has been converted to task being worked on – either manually by making it a task node or by adding a new tag like "#in progress".

With ${sys:doneTime} it could then be used as a time logger for tasks:

1. Create task as a plain node.
2. It's waiting for its time in some kind of backlog.
3. Decide to make it more actionable - tag is as "#in progress" or convert it to todo (or both).
4. Complete the task

Why is this a problem for you?

I have a long list of illustrations to be created. When I start working on an illustration task, I convert its node to a todo. After finishing the illustration, I complete its todo.

I would like to track the time from "start working on an illustration task" to "complete its todo".

Suggest a solution

Have functional:

• ${sys:convertedToTaskTime} or
• ${sys:taggedAs{{CUSTOMTAGNAME}}Time}
  to be then later used for example as a date ranges in Calendar View.

Explain the problem as you see it

There is no way to use fields, especially system fields (created time, done time), other than one specific "Date" for more flexible events/tasks log in calendar view.

Why is this a problem for you?

ATM calendar view is not as useful as it could be.

Suggest a solution

Checkbox "Use separate date fields for start and end time" for opening second Date field menu to choose it ;)

Explain the problem as you see it

Closing a dock is permanent, to open the node in the dock we need to do it again, manually.

Why is this a problem for you?

When using docks sometimes they are:

• not needed for some time
• are frequently needed for a second.

In both cases, it would be very useful to hide/collapse/minimize dock(s) with an easy way to show them again in the same format as before hiding.

Suggest a solution

Collapsible/minimizable docks with an indicator on the browser window’s edge like an arrow similar to iOS picture-in-picture window hidden outside the screen.

Open collapsed dock when:

• Pressed keyboard shortcut and/or
• Moved the mouse to the corresponding browser window’s edge

Explain the problem as you see it

There is a huge potential for Tana in improving functions which get information from node properties and fields and show them in ways customized by user. Custom set of icons would be one of them.

Why is this a problem for you?

I don't have a robust way to customize how nodes are presented to me. Icons could be used to show:

• type of node as a connection to #supertag
• type of node with field value (like custom tasks statuses or - in my case - illustration tasks' statuses where I need to have 2 connected at the end structures of statuses (not done/to delegate/delegated/done/to fix and not done/awaiting/in progress/done/to fix).

Suggest a solution

Set of icons available to use in similar way to checkboxes. Additionally emojis.

Nice to have would be interaction with the icon by choosing one from the list thus e.g. changing it's status or supertag to another one from specific list of options.

It could be also accomplished by improvements to "Build title from fields" feature.

Explain the problem as you see it

There is no search way to remove fields' content.

Why is this a problem for you?

I sometimes need to remove stuff from fields used in "Build types of fields". Removing it via the command line would be helpful and would spare digging through the collapsed node and its fields, especially hidden ones. A command via CMD+K would allow for assigning a shortcut for it also.

Suggest a solution

Command to set the field's value to empty.

Explain the problem as you see it

When a node has "build title from fields" feature enabled and uses a field with a node also using this feature it grabs its whole title (with text from "build title from fields", not only from ${name}).

Why is this a problem for you?

It messes up some of my workflows. E.g.:

1. “wer” tagged as #wytyczne is a node name, and gray text after it is built with “Build from fields” feature.
2. The block of text tagged “#cytat” is also built from fields, including “Źródło” field which has “wer” with text genereated from fields).
3. I would like a block of text to look like

text /wer/21 #cytat

instead of

text /wer PTK 2010 r. – Rozpoznania EKG/21 #cytat

Suggest a solution

Two different parameters in "Build title from fields":

1. ${name} – using whole node text, with "Build title from fields" if it is
2. ${title} (or similar) – using only nodes title, stripping out anything built with "Build title from fields".

Explain the problem as you see it

There is no way to easily differentiate between done and dropped tasks.

Why is this a problem for you?

I need to use <Build title from fields> to add some kind of emoji for differentiation between done and dropped tasks. It would be much easier, less confusing, and more elegant if it was shown by different checbox icon.

Suggest a solution

Add the third state of a checkbox – dropped, like in the image below (from Things 3 app):

It will be an addition to existing checkbox states:

• Done (tick),
• Not done (empty).

Explain the problem as you see it

1. Switching from other PKM tools can be sometimes tiring if we are used to using (( and [[ for references (e.g. in Workflowy (( for mirrors aka references and [[ for inline links aka inline references).

2. There is no way to specify right from the start of typing node content that we would like to put an inline reference in the beginning of a node – we need to use "@" and then Shift+Enter but sometimes the flow isn't as good as it can be.

Why is this a problem for you?

Differentation between inline referencing and referencing at the time of adding them can be sometimes problematic.

Suggest a solution

Converting:
(( to “@ as a reference”
[[ to “@ as an inline reference”
(with leaving bare “@” exactly as it is now).

Explain the problem as you see it

There is no way to change value of node's nested field via command line (and to create a custom shortcut).

Why is this a problem for you?

Filling in nested fields (especially in multiple nodes) is time consuming.

Suggest a solution

"Set Field" command working with all types of fields giving a prompt to type in Field content, with an ability to referene other nodes.