One of the great things about WorkFlowy is that there is no difference between a category, a note, a task, or anything else you create. All of them are just bullet points.
This means it’s easy to turn notes into tasks (by assigning people to them) or add notes under tasks (simply by adding more bullet points under them). It also means you never need to waste time thinking, “Is this a task? Is this a note? Is this a category?” – you just start typing.
Tagging is a powerful feature that lets you add additional layers of organization to the normal WorkFlowy hierarchy. We use them all the time at WorkFlowy HQ.
We recommend using @name tags to assign tasks to people on your team. We add the@mike and @jesse tags to tasks to assign them to ourselves. You can add easily-accessible tags to root level of your list to see all the tasks assigned to a person in one click.
(We’ll be adding a tag list feature to automate this process in the future.)
We also use #current and #next tags to indicate which tasks we’re working on now and which ones we intend to work on next. That means I can search for “@jesse #current” to see what Jesse is working on right now. The simple combination of @name tags and #current is quite powerful for project management.
Tags are versatile. Another way we use them is for our bug tracker, which is a list of all the bugs we know about but haven’t fixed yet. (Did you think we use one of those slow, bloated dedicated bug trackers? Of course not. :) )
This is a screenshot of the top of our bug tracker:
Our bug tracker is a flat list of bugs that are tagged into platform and categories. Platforms include browsers and mobile OSes (#chrome, #firefox, #ios, etc.) and categories include things like #collaboration, #controls, and so on. We list these tags in the note under the “Bug Tracker” item, which shows up above the list of bugs.
Click on a tag and you see only the bugs relevant to that tag.
We also have a #NEXT-RELEASE tag that we sometimes use to tag bugs that should block our next release.
Whenever we fix a bug, we “complete” it, which hides it from the list. (We generally always hide completed items, which you can do with the control in the top right. We use the “complete” feature both to complete tasks and to archive old stuff that we don’t want to see any more.)
These are just two of our uses of tags. We’ll go into more in the future.