Christo Olwagen

Yes and ... can we have the ability to apply this keyboard shortcut to multiple nodes concurrently?

Use case: I am doing a project status update report. I have the bullet points from the previous report in the node, and I want to strike them out in bulk and put new comments above them

Maybe add this as a display option in the view settings?

This is critical for me as a freelance consultant that needs to work with different clients and different suppliers working on parts of a project.

I like this idea a lot!

I recently tried the Zapier AI assistant that tries to convert a verbal description of a workflow into a zap - it did not work well for me but that might be because of the google calendar interface api / zapier configuration which is decidedly unfriendly (not sure if this is a google problem or a zapier problem).

Given Tana's deep integration with AI already, being able to map a workflow process like this and having the AI turn it into commands would be awesome. I use Miro for process mapping but I am sure that the ability to turn that into a workflow in tana would make me switch.

I am not sure if this will solve your problem, but I have search nodes in my day tag that show me all nodes that meet the criteria [[edited last x days]] or [[done last x days]]. i filter these for nodes with specific supertags, but a quick check suggests that it will pick up ALL nodes if you don't filter the search.

yes please. it is theoretically possible to sort the table by the field you want to use for swimlanes, or filter it out, but it would be great to have swimlanes.

I also want a timeline view for those sequential tasks, especially the repetitive ones. (a gannt view could function as this in a pinch)

The more I use TANA the more I realise how useful dependencies would really be!

Supported - I would use it for planning and review purposes that span two weeks or 2 months or quarterly milestone planning. I know some people also work in 45 day cycles rather than 90 days (one quarter)

agreed! especially where those are linking fields between data clusters (e.g. client <-> project) where the client CRM data is essentially not deeply integrated in the task / todo structure of project management

1st priority: setting the default values based on ancestor nodes or sibling nodes
2nd priority: required or not required
3rd priority: display or hide when empty

side note: would this be hard to do if it is in an extended supertag? e.g. fields in todos inherit from the parent node but a project which could be an extension of the todo base tag inherit from the associated client node

nice to have: move it up or down in hierarchy when it is from an extended supertag

I like this idea! Going with an excel (typical spreadsheet) function makes it more accessible. One tricky tech question would be if it could / sould allow multiple "if" statements in sequence, and/or nested "if" statements (I can build some pretty convoluted stuff in excel if I am in the mood to really dig into large datasets)

One possible use case for me would be when I have a scheduled date that is past a due date. The title can then have a "overdue" indicator (!) behind the scheduled date (or make it red, in a glorious future where we can put formatting strings into titles). If it is not yet overdue, the scheduled date remains black with no enhancements.

whilst we are on the topic, can we also change the display properties of inherited fields? in lower level tags I might want to always see them as they are relevant there, but at higher levels I would be quite happy to hide them. especially as I need to use fields up and down my stack to allow better searches of child and parent nodes (until Tana gets that natively)

I am not a big fan of Gantt charts, but currently run my business on ClickUp. I would say that their implementation is not great (sometimes if feels like they go for quantity of features rather than quality).

The specific problems I have with their implementation are

1. changing dates on tasks do not automatically push out the dependent tasks
2. There is only F-S (finish-start) dependencies. If you go geeky on Gantt Start-Start, Finish-Finish and other dependencies are important for managing actual vs plan variance
3. There is no lag implementation (e.g. starts 3 days after the previous task finished).

^^^ these push the Gantt features towards the realms of proper project scheduling tools, but I think a simplistic implementation purely for visualising timelines, whilst useful for comms purposes, are not so useful for functional utility

Request for custom date format supported: European for me - dd/mm/yyyy and week starting on Monday