![]() This workflow really combines two new features, tags plus granular notifications. It’s a massive pain in the neck to get logged in, and that process started so now, with a tag, I can easily get a list of all those filings (regardless of project) once I do log in to the creaky government flash-based website and batch the filings all at once.Īnother use for tags in my experimentation so far is to get much more granular with location. For example, I’ve created a tag that relates to a very specific online corporate filing I do for some of my legal clients. I’m also experimenting with certain classifications of work. I’ve been experimenting with tags based on energy level, so when I’m in the afternoon doldrums, I can have OmniFocus show me just a list of “brain dead” tasks I can check off without needing to concentrate. This isn’t, however, limited to just locations and people. I could then create a custom perspective based on those two flags so, when Daisy is around at home, I can filter down to all tasks holding down those two tags. Using the above example, I can put a task that has both the “Home” and “Daisy” tags applied. You can now put any number of tags on a task, giving you much more power to filter tasks. However, with traditional contexts you could not qualify a task by both a person and a location because there was only one dimension of a context. ![]() ![]() For example, some tasks can only be done on your Mac or with a certain co-worker. Traditionally, following GTD cannon, context was used to put a task in a certain place or with a certain person. The benefit of tags is that it adds a lot more dimension to ways you can slice and dice your tasks. With the new version, context has been replaced by tags. Traditionally, OmniFocus had three ways to index a task: by project, by context, by flag status. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |