Hierarchical tags are powerful instrument to categorize your tasks in many different ways simultaneously.
For example, if you want to tag your tasks by Priority, that can be Important, Medium, and Low and by Complexity, that can be High, Medium and Simple, then the tag hierarchy should be the following:
Tags for a certain task, consequently, will look like the following: “Priority/Important, Complexity/Simple”.
Please note, that in the example above you can't simply use “children” tags to categorize tasks, as both Priority and Complexity properties have “Medium” value. In addition, 2-levels hierarchy improves tags readability and saves users from the confusing attempt to guess if “High” is a “High Priority” or “High Complexity”.
However, in simple cases it may be more convenient to use 1-level hierarchy. For example, consider grouping tasks by “Important”, “Not Important” and “Complex”, “Not Complex” tags. Such scheme won't confuse users, so tasks can be simply tagged as “Complex, Not Important”.
Depending on situation 1st-level parent task may be used as a tag itself.
Consider the following tags hierarchy:
It classifies tasks depending on if something new should be done, or completed work should be improved. Improvements can also be tagged depending on their severity.
In this example 1st-level Improvement tag makes sense itself and severity classification can be considered as optional, for example task can be tagged just “Improvement” if severity is not clear. At the same time at the very first example tag “Priority” itself makes no sense if used to mark tasks. It should be always followed by a 2nd-level tag.
We suggest to make an agreement between your project or area members regarding which parent tags can be used stand-alone.
We recommend to perform regular tags review using Tags Management panel, to keep your project tags consistent.
Best Practices >