Ability to mark tags as 'global' or 'collection' | Voters

Ability to mark tags as 'global' or 'collection'

planned

Martyn Bramall

Be really useful to create sets of tags specific for the current collection and also to specify a series of tags that are global across all collections.

This should help prevent the huge glut of tags presented which were created for other projects when adding a tag to a card!

June 9, 2020

Niklas Westman

Is there an ETA for this? We are currently avoiding tags as it just does not work having them global for us. We would however really want to use them

Hans Dahlström

Can one solution be that if you create a custom tag column, or a local tag column, you have the option to have your own custom "tags space" where tags are only created, used and visibile in that column

Markus Halttunen

Hans Dahlström: How would it work in the situation where the card is moved e.g. from a backlog with the custom tag column to a board on the same collection? Would the tag still be visible in the card?

Hans Dahlström

Markus Halttunen: yes

Markus Halttunen

Hans Dahlström: In that case, it might work. It's a bit difficult for me to fully understand how things would work in your description. Can you elaborate why you want to treat tags on column level instead of collection level?

Niklas Westman

Hans Dahlström: I think we can benefit from the possibility to create multiple global tag columns. So you can choose which global set of tags that fits a certain board.

Hans Dahlström

marked this post as

planned

Rob Goddard

Hans Dahlström any update on this feature? We do not find Tags useful without this

Alex Hartpence

High priority indeed IMO

Markus Halttunen

The current situation is really problematic. We have hundreds of tags in the organization. 
You can already limit tags to certain people or groups. It would be even more logical to limit tags to certain collections. The UI could already suggest the relevant collections because most tags are already in use only in 1-3 collections.
If a card is moved to a collection where the tag is not allowed, nothing needs to change. The card can still have that tag but it can't be used for the other cards in the collection. This is in line with a card that has a person assigned to it even though it resides in a collection where the person doesn't have access to.
Mentioning Hans Dahlström because the current solution is so messy and I really think this improvement should get priority.

Mohamed Nazeem

Now tags are seen every where, what makes sense for one collection looks awkward in another collection. Better to classify or make tags specific to collection.

Richard Morton

Should also have the same functionality for Card Templates, so they can be project specific or global