How about introducing a new feature to insert a date or number as an attribute of tags? For instance, we may need to insert two dates, one for the due date and the other for the date I actually completed. In the case, we can insert e.g. @due(2018-07-01) @done(2018-06-30) to the task. Another example can be @priority(2). TaskPaper is supporting the feature and I found it is useful for many cases.
24 Likes
Yeah I like this idea, it could be a flexible way to setting priorities and for time-tracking.
Please like or comment if you like this feature request, and if enough people do weāll add it to the Trello roadmap 
9 Likes
I love me some tags! And I love that you guys are taking on all the stuff that workflowy is ducking But workflowy is simple, to the point of being simplistic. So in WF for really important tasks I just append with four exclamation points, the b list gets three !!! and so on.
The nice thing is that you then just go to the search box, type in four exclamation marks, and you see the short list, you delete one of those exclamation marks and you see the bigger list and so on.
Iām all for functionality, and if it helps people thats fantastic, but I wonder if its a really big hammer for this nut?
1 Like
Two reasons why I think this is worth it:
- It does not bother people who donāt use it, at all, unlike the four menus that you never use in Photoshop. You can just pretend it doesnāt exist and it wonāt affect you one bit (at least we hope we can make it so).
- Itās super flexible for quantitative data. I know you can workaround @priority(4) with ā!!!ā, but it harder to work around some other cases, like tracking time with @spent(5) or assign tasks with @assigned_to(amanda) vs @assigned_by(amanda). With plain tags, it can be hard to search for items that are assigned to amanda without seeing stuff that are assigned by amanda, unless you add specialized tags for both (#assigned_by_amanda and #assigned_to_amanda). There could be workarounds, just like how people work around dates in WorkFlowy, but itās different than being supported natively, just like it would take a crazy WorkFlowy extension to sync those custom dates to Google Calendar.
Of course, this is just my current thoughts, could change anytime in the future. No plan to act on this immediately.
We originally got this idea from TaskPaper, after a user suggested it. Link to TaskPaperās doc: https://guide.taskpaper.com/reference/searches/#attributes
6 Likes
I really like this idea. It expands tagging from simple on-off flags to key-value attributes. This would be huge for tracking and data analysis. Thanks for considering it.
3 Likes
Fantastic and responsive support! Thanks.
1 Like
Super cool, really appreciate the thoughtful kind answer. Hey while weāre here, can I bend your ear about something else - cuz this brings up another point as to how you are using these different hashtag types.
So in the past (yeah yeah Iām all Stockholm syndromed from WF) Iāve used @ for people. And Iāve used # for verbs and nouns.
So one entry might be ā#call @Amandaā
When I click on #call I can see everyone I should call, including Amanda.
And right before I speak to amanda I click @Amanda and boom, I get the full history of when I spoke to Amanda in the simple calendar function I run in the outliner - because every time weāve spoken in the past, Iāve made a brief note and tagged it @Amanda.
Here it seems you are using @ and # in a more expansive sophisticated way. But it also seems a bit looser.
For example what I was expecting when I clicked on the ātagā list view was to see all the @people followed by all the #verb/nouns. What you show, of course, is all the tags alphabetically regardless of # or @.
Iām wondering if it would be possible to have, for us simpler folk, a bifurcated list option with the @'s and #'s grouped. That way I can quickly look through my address book for someone. The way its currently implemented seems a bit chaotic to my eye.
Or maybe there is way of filtering the tags? - if there is, please let me know! Or maybe Iām thinking about this all wrong, and I should just make everything a #, including people? Would love to hear your thoughts on this.
Thanks for continuing to expand my horizons and this product. Very cool.
2 Likes
Just to clarify, regarding the ālistā, are we talking about the list when you type # or @ (auto-completion list), or the list in the tag pane on the left (which is a Pro feature)?
Thanks!
I was talking about the tag pane - the good news is as soon as you hit # or @ you get just that list as it autocompletes. Maybe thats good enough, I guess just when I saw the tag pane list I expected to see all the @people grouped together. But it seems you are probably using @ in a more sophisticated way than me.
Thanks again.
Iād say thatās coming soonā¦ once alphabetical sort in tag pane is in place, sorting will automatically group # tags together and @ tags together.
1 Like
This would be spectacular. Just to contribute to the conversation, I find that most things I need can already by done with the current features:
- #assigned(@person)
- #reported(@person)
- #priority(1)
The only thing that is completely missing ATM is date parsing when a date is a value of an attribute (in TaskPaper lingo):
- #due(2018-01-01)
Also, if and when tag attributes are added, it would be nice to be able to query both dates and numbers with gt, gte, lt, lte operators.
Congratulations again on a truly fantastic product and even more fantastic relationship with your user community.
Yeah, dates will be more tricky. A UI might help though. Example from a chat app:
Thanks! And we thank you for being in this community and making such amazing contributions to discussion. 
1 Like
That does look pretty awesome!
Imo a very closely related feature of Tags colud be the temporal inheritance of parent Tags for search results.
I have started testing / theorycrafting Dynalist 1-2 weeks ago, and the only thing keeping me hesitant about going Pro is this.
The current workflow design is this:
I place āroot-tagsā into the first comment line of the Document title. Things like #[ for any action item , @a for application name beginnings etc.
Below the first Bullet point is the full tag-matrix. that contains the completion of the root tags.
For action items for example: #[] #[!] #[1] #[2] #[3] #[II] #[Ć] ; for others like @a.Dynalist.
Punctuation caracters within Tags have the benefit in search field that they allow combining.
*Edit: due to certain seach rules, better to add a dot before numbers in the aboveā¦ like #[.1]
So this way i dont have to type anything, just click on a root tag and then click on some more related tags that will show up from the tag-matrix.
This is proven to be very fast and effective to reach to any specific content rapidly.
Here comes the problem, shown in a simple scenario:
If I was about to store content for example grouped by month, giving the parent the name or tag #November.
If let say Iām looking for #iDea s from #November the only way to find them would be if I added the tag #November to every single item below it, because if I select both tags in the searchfield it will show 0 results.
I can imagine scenarios where the more strict filtering is benefitial, so maybe It could come as a selectable search option, just as when I decide if Im searching locally or globally.
Iām thinking now for days how to come around the above problem without āovertaggingā every item, not so much luck yetā¦
Please guys and devs comment on this.
1. Can you think of any better approach / workaround to unbreak my system?
2. Or if you also feel the potential in the suggestion, can you make this āsimple?ā feature part of the upcoming Tag-attribute update?
Screenshots for better understanding:
ā So far so goodā¦ now lets sketch a real life scenario: ā
If I want to search for #[] todo-s of @h.Angie all over the notesā¦:
Results are none
Unless I start overtagging:
To reach:
ā¦ so how to come around that??
Well I have figured one quasy-workaround, but not fully convinced yet ā¦ 
(Putting all content in the comment field instead of separate sub-nodes)
To combine the best of two worlds (nodes and comments) maybe a LOCK feature could be applied. If a lock is ON for a node it would mean that all subnodes count as āpart ofā the mothernode - that would allow making more flexible notesā¦ If the lock is OFF, child nodes would behave as they do now.
3 Likes
Anyone reading this, you can now handle this using the āancestor:ā operator ;^)
1 Like
I also really like this idea. You could easily implement something like start-date or review-date and filter by it. This is really helpful for taskmanaging, especially when using gtd or master your now.
I think most taskmanagers are main focused on due-dates. I got loved to only use due date, when it really is due. Often date is something like I want to think of that again on that date. Or I plan to do it if possible at this date, e.g.
This is something different than due date.
Currently I have a bookmark, that is filtering out all items, that are in future. I want to hide them for now. However If there is a real due-date this is limited. I have a workaround using a timespan instead, where the last date is the due and the first date the āto-showā-date.
I think having tag attributes would make this handling clearer and more easy.
I just want to add that I also really like this idea!
A really rough current workaround for attributes of numbers is to use dates in child elements along with āsince:ā and āuntil:ā instead of greater than and less than.
E.g.
- My Dynalist element
- @percentComplete !(1-1-1085) (representing 85% complete)
Then I can search ā@percentComplete since:1050 until:1090ā to find elements ātaggedā as between 50% and 90% complete.
But certainly a proper implementation similar to TaskPaper would be much much better 
Great idea. Also familiar with it from TaskPaper. Is this on the Roadmap for Dynalist?