Tag View - One tag per topic

  • 1
  • Question
  • Updated 3 weeks ago
  • (Edited)
Tag view seems to be entirely dependent on Topics only having one tag - WHY? Why is that a sensible thing to do?

Am I missing something? Are there lots of MindManager users who only ever use 1 tag per topics?

I have multiple tags that I use within my MindMaps to track state and progress of topics.

This is a problem when taking existing topics from other mindmaps into a Kanban.
Photo of Jim AK

Jim AK

  • 92 Posts
  • 3 Reply Likes

Posted 3 weeks ago

  • 1
Photo of Alex Gooding

Alex Gooding, Champion

  • 959 Posts
  • 232 Reply Likes
You are correct that tag view works if there is only one tag per topic, but this restriction is only within the tag group nominated by the user for the tag view. You can have multiple tag groups each with separate sets of tags, and switch between groups in tag view. The same applies to icon groups in icon view.

It is difficult to see how tag view could work with topics having multiple tags from the same tag group. Either the topic would have to appear multiple times, or only once, based on some arbitrary precedence within the group. Both options would be potentially misleading.
Photo of fsmontenegro

fsmontenegro

  • 9 Posts
  • 0 Reply Likes
Same here! It's not so much one tag per topic that annoys me, but that tags have to be 'exclusive' to be supported in the Tag View. For example, now I can't have a "Features" tag group and "feature A" and "feature B" as specific tags that I could add to a topic and see it in the Tag View. Very annoying :-(
Photo of Alex Gooding

Alex Gooding, Champion

  • 959 Posts
  • 232 Reply Likes
I can see the benefits in certain circumstances like the one you describe, but in most other cases - for example, Kanban - it could cause a lot of confusion. It also means that one of the great features of tag view, the ability to change a topic's tag simply by moving it to another column, would be very difficult to implement.

It would be good if there was an option to allow tag view to show topics with multiple tags in the same group, but I think the restriction of showing topics with only one tag per group should be the default. There would also probably have to be an upper limit on the number of tags a topic could have within the one group.

There is a workaround of sorts, providing there aren't too many tags or possible combinations of tags in the group. In your features group for example you could have Feature A, Feature B and Feature A+B as separate tags. If that is problematic for other purposes - for example, if you are counting tags in Marker Index - you could use Smart Rules to generate another set of tags in a separate group specifically to use in the tag view, with one tag per individual tag or combination of tags from the original set.
Photo of fsmontenegro

fsmontenegro

  • 9 Posts
  • 0 Reply Likes
I see your point, of course. I think for Kanban it makes sense to enforce 'single value for Tag group' as topics move between columns. The Tag View, however, is not restricted to Kanban maps, so the restriction of single value per tag group could very well be a default, but something we could switch off.
I use Tag View to track vendors in the space I cover (I'm an industry analyst) and now my coverage is a mixture of maps with tags when I can and Excel for situations where I need multiple values per tag group. Not ideal...
Having combinations of Tag values is something that quickly spirals out of control... :-( n^2 :-)

Hoping it gets revised at some point.