Or there is some other better approach to deal with my use case?

I agree it is essential to be able to see the tags. If I cannot see them I cannot verify my tagging and cannot trust my tags. I have almost stopped using them completely, but I would use them if I could see them.

Totally agree. I miss seeing tags in the task line.

@Folke @joaquinmari @shandr
Hi,

Thank you for your feedback.

Sorry that it is not in our developing plan to show the tags on the task bar. There will be too may information which may take your attention away from the task itself.

@shandr
You could try to use context to mark the task. Everything is done in a special place or under a certain circumstance, and that PLACE or CIRCUMSTANCE is called Context in our app. So you can add tasks with certain contexts and view the tasks with the same context together.

Shall you need any help or have additional questions, please do not hesitate to contact me back.

Thank you for your support!

Best regards,
Doit.im Team

Actually I tried Context before submitting this issue. But there is a problem: you can't assign to 1 task several Contexts. And there are many tasks in my case that should be assigned to several persons. So it's not usable in my case :(

@wendy_only, you said "There will be too many information which may take your attention away from the task itself."

I would say that is a matter of judgement. You might say that about context and project and everything - less info is of course cleaner, but it is not only a matter of what is clean and elegant, but also of what is functional.

Please bear in mind that both Doit's Contexts and Doit's Tags are in fact CONTEXTUAL REQUIREMENTS for being able to do the task, e.g. a location, person, mood/energy, clothing/attire etc etc that are necessary. If we cannot see them in the list we cannot verify that we have applied the correct situational requirements and therefore cannot really trust or use the feature at all. I personally only use the Context feature because of this, and that is a great pity.

In fact, since both Contexts and Tags represent situational requirements (GTD energy, GTD contexts etc), I think you should harmonize your Context and Tag features and make the part of one single feature. I think maybe the best solution would be to let the Contexts be a manually selected (small) subset of already defined Tags - the Contexts are useful for list grouping and for easy access via the left menu. In those cases you do not want to see too many. But all Tags (both Contexts and regular Tags) should be visible on the task line. It is up to each user how much info he/she wants on the task line. It is necessary to be able to see them. Otherwise we cannot trust our tagging. (If you are concerned about how it looks you could implement a simple list toggle to show/hide all the rest of the tags.)

@Folke
Hi,

Tag is different from Context and Project. Tag is used for filtering tasks. Tasks with specific tags can be filtered out by tags.

In Doit.im, you can at most add 5 tags for a single task.

BTW, could you please give me some suggestion how to show the information if there is no enough space on the task bar, especial on the mobile apps?

Best regards,
Doit.im Team

In Asana tags displayed as I described in my first message. It's really useful. Imaging the situation: I have 20 tasks in my task list, I have 2 tags that should be used in this list(for example: learn and do) and I need to understand whether all tasks have one of this two tags. What should I do? Constantly switch between tags and count how many tasks disappeared and how many left :). It's really cool feature.

@shandr
Hi,

Do you try the tag filter feature? You could filter the tasks which have the same tags in list. You also could create filter by advanced search to review all tasks with the same tags.

Best regards,
Doit.im Team

@wendy_only

I apologize for not answering your post #7 above sooner. I did not notice it until now.

You say "Tag is different from Context ...". Yes, it is true that these are two different features in Doit, but no, it is not necessarily true that they represent different kinds of things. Most users probably use both features for situational requirements of various kinds, such as necessary tools, places, persons, mood/energy etc.

The two features have different advantages, and people probably try to make the best use of both. The advantage of using the Context feature is that we can group the lists by it, and we can assign a Context quickly by drag-and-drop and we can see it in the list. The advantage of the Tag feature is that we can "quick filter" the list by it (using the tag bar). But both features tend to represent situational requirements (people, places, energy etc).

For example, for me personally, I want only a short list of Contexts because I do not want to have too many groups when I group by it). Tasks that require some particular person I always mark with the Context @Person. In addition, I have specific individual Tags for my most frequent contacts, but since I cannot see these tags in the list they are often wrong, because I often forget to add them, and I usually do not discover my error because I cannot see the tags easily enough, so basically I cannot trust my tagging and do not and cannot really rely on tag filtering. I also have tags for High Effort etc that I also cannot trust. This is a great pity.

I think that good tagging and filtering features would be very attractive for many users. One step is to simply make them visible, just as they once were in your Windows version. Another step would be to introduce elimination filtering (NOT filtering), which would enable people to save a lot of tagging work and also enable people to eliminate all tasks that are clearly impossible today and thereby have a shorter list to make an intuitive choice from. Another very good step would be to harmonize the Context and Tag features, such that both can be used for quick filtering (tag bar).

As for harmonization of the Context and Tag features, instead of allowing users to create an entirely "new" context from out of the blue, Contexts could be defined by the user instead electing a few of his/her already defined Tags. This would ensure that all situational requirements are at least defined as Tags (available for quick filtering). Those of these situational requirements that are desirable for list grouping are a subset of these, and if a user has applied more than one such Context the tasks would be shown on the first of these context groups.

A further step to make all this very powerful and elegant would be to introduce hierarchies of Tags. This would allow detailed tagging without incurring extra tagging work. For example, if I have the a Tag called John defined hierarchically "under" a Tag called Person, and if I have the Tag Person elected as one of my few Contexts, then I would only need to apply the Tag John to still be able to see this task under the list group called Person.

You asked: "... could you please give me some suggestion how to show the information if there is no enough space on the task bar, especial on the mobile apps?"

Sure I can. Perhaps the simplest solution, and probably good enough, is to simply continue with tags and wrap the lines if the space is not enough. It is up to each user to define and apply only as many tags as he/she is comfortable with. Another way is to stop at the end of the line and just add a little icon etc to indicate "more tags...". There could also be preference options for all this.

Hello Folke,

Any feedback from this, I am really hoping for all of the above, but for me at least being able to bulk tag, would greatly speed up my workflow!

I use tags to associate tasks to people that I am working with on the task. Just adding the ability to search by tags in the search function would help (tag: personame). The problem with creating filters is I need too many, and constantly editing one and refreshing the page is slow. Somewhat like context it enables filtering tasks I discuss with an individual, and often more than a single person is associated with a task.

This is also one of the main features I missed in doit.im. I've recently switched to using the much more simple (and far from what I want from a GTD program so far) Trello because I feel like their development is headed in a more promising direction (and they show their users what they plan on implementing in the short-term and long-term future).

+1 This feature is really missing. I cannot rely on using tags without being able to see them listed.