GitLab

Now that's a hard one. Currently, TimeRanger allows to add any count of unique tags. But if we look closely to what tag is, we find out that it defines a value of some property. For example, tags Home, Office and College are all related to places. Let's assume that you can't do something in Home and Office at the same time and divide our tasks following that principle. If you did it right, for each task or activity we can get a list of tags and also a list of properties which those tags are representing. Let's call some property like that a group. So Place - is a group, Type (like Rest or Work) - is also a group, there may be Priority (High, Medium, Low, Urgent), etc. So now on, each task or activity still may have multiple tags, but only one of each group. Suggestions should now be formed using data about currently specified groups. Adding a tag of group that's already presented in chip view should lead to cancellation of operation. There also should be added an undeletable default group "Common" in which new tags are being pushed at start. Implementation of tags groups leads to improvement of analysis and ability to slice multilayered pie of data getting some nice visual effects. But that's another story.