Cullen

Explain the problem as you see it

As far as I am aware, there is currently no way to assign unique numbers to tagged nodes in a way that prevents duplicate numbers.

This is particularly challenging when prioritizing tasks, as it can be difficult to ensure that each priority number is only used once. For example, if I have five, high-priority tasks that I would like to handle in a specific order, it would be nice to be able to assign them numbers 1 - 5, so I can sort on this field, and clearly identify which ones I need to focus on first.

Without this feature, managing task priorities can lead to confusion, as multiple tasks might be assigned the same priority number unintentionally.

Why is this a problem for you?

When managing a prioritized list, I need to assign unique numbers to each item to indicate its priority. Without a number picker field that ensures uniqueness, it becomes cumbersome to manually track which numbers are in use, leading to potential overlaps and mismanagement of priorities.

Suggest a solution

Develop a number picker field in Tana that allows users to assign numbers to tasks, with each number being unique and not duplicated across records. This field should also display available numbers, making it easy to assign priorities without the risk of overlap. This feature will help maintain clear and organized task prioritization, improving overall task management.

Explain the problem as you see it

There is currently no way to automatically assign a unique, incrementing number to each new record. This becomes problematic when you need a reliable and sequential way to identify records, such as when managing an inventory or tracking cases. Without this feature, users have to manually enter these identifiers, which is both time-consuming and prone to human error.

I understand node IDs are unique. But I am referring more to the record itself. When using Tana for database or CRM type purposes, it is crucial to have a custom field that can be configured to automatically increment with each record.

Why is this a problem for you?

I often work with large datasets and need a consistent method to track records uniquely. The absence of auto-incrementing fields means I have to manually keep track of identifiers, which increases the risk of errors and complicates my workflow, especially in situations where unique identification is critical.

Suggest a solution

Implement a feature that allows the creation of auto-incrementing number fields within Tana. Each new record should receive a unique, sequential number automatically. This will ensure consistent and error-free tracking of records, greatly improving efficiency and accuracy in managing data.

Ideally, this field would be customizable. The ability to set the starting number, and the increment amount would very helpful.

For example, starting the numbering at 4 (4, 5, 6...) vs. (1, 2, 3...) or incrementing by 3 instead of 1 (e.g. 1, 4, 7, 10...). One of the most frustrating part about traditional auto-increment fields is that they are very rigid, and not great when importing existing data that does not start at 1.

Explain the problem as you see it

Currently, the Relative Date [terms] are limited to:

Present time: Today, this week, this month, this year
Past: Yesterday, last week, last month, last year
Future: Tomorrow, next week, next month, next year

Obviously these can be customized by specifying the number of said-term.
e.g.
IN 2 WEEKS
IN 3 MONTHS
3 WEEKS AGO

But this does not always allow the user to accurately target the date they are hoping to target, especially if the command is automated.

I would like to be able to ensure that any work-related tasks or follow-ups etc, are scheduled during the work week.

I believe that there are a lot of use cases for this feature, and would be extremely useful for people using Tana for work purposes like task and project management.

Why is this a problem for you?

I have a supertag called #follow-up that I use to track items at work that I may need to follow up on. It is an extension of my #task supertag. One of the unique fields it has is a date field called Follow-up by. This is the date by which I expect myself to have followed up on the item in question, assuming I have not heard anything back already.

Currently, I have an "On added" command configured that automatically sets the Follow-up by date to 3 days from the day the node was created.

The issue that I have is, if I create a #follow-up item any day from Wed-Fri., I would like the Follow-up by date to be set to the next 3rd WEEKDAY. So, for example the dates would be set like this:

Suggest a solution

Add more Relative Date [terms]

I would like to see the addition of Relative Date [terms] that allow us to specify specific amounts of time based on WEEKDAYS (BUSINESS DAYS) vs. WEEKENDS.
eg.
IN 3 WEEKDAYS
IN 14 WEEKDAYS
IN 2 WEEKENDS
IN 3 WEEKEND DAYS