Settings and activity
1 result found
-
10 votes
An error occurred while saving the comment An error occurred while saving the comment John Kim Murphy commentedI would also like to be able to sort by this date. So a long-term parent task like "read book by next week" can be "bumped up" in the sort order by adding a child task like "read chapter 1 by tomorrow."
John Kim Murphy supported this idea ·
If it makes this feature more worthy of implementation, my use case is more generalized. I call my idea "deep tags" because they are an extension of TaskPaper tags, where a due date would be marked with a tag like "@due(2019-08-08)".
I wish an item could have an additional due date which is based on the value of child items as described others here. I will call this tag "#due" using a '#' sign to indicate it's a deep tag. However, it could be called anything, like "@effectiveDue" or "nextDue".
This concept could be extended to other deep tags: #count, #min, #max, #sum, #avg, etc... You could even have user-defined deep tags by running a script that looks like deepTagName(defaultValue, item, childItems[]){ CODE}.
Besides the due date use case discussed by others, here's a use case for #count. Your sales pipeline has many stages and you tag where each prospect is in the pipeline (like: "idea", "gather contact info", "touch", "demo", "won", "lost".) The deep tags like #count(idea), #count(touch), #count(won) would automatically count how many are at each stage, which is valuable information.