Global tags setting

[GitJamz]

Well I believe this is a must have. I want to setup tagsystem like "low" "medium" "high" "urgent" - tags.
But I dont want to need to do this on every single board. There should be a global tagging system. I almost dont even see the reason behind isolating tags for a single board..

[stefan-niedermann]

A workaround could be the "clone board" option - you can create a "template" board where you can set the lists and tags you like and everytime you clone from it, the lists and tags will be cloned, too (without cards).

[GitJamz]

A workaround could be the "clone board" option - you can create a "template" board where you can set the lists and tags you like and everytime you clone from it, the lists and tags will be cloned, too (without cards).

True this is a workaround that works. But I dont see why this should not be implemented as a function in this project.

[putt1ck]

The reason a global tagging system isn't useful is because boards get used for all sorts of processes; so a "universal" tag system would just be noise - it would need 100s of tags (and for tags to have i18n support and translations for all those tags) to fit the different use cases. For example we have boards for building projects, where the concepts of "low" "medium" "high" "urgent" make little sense (and the first 3 would be confused with risk levels for sure), and boards for IT issue reports, where the tags are used to indicate probable causes and urgency is dealt with by human assessment and allocation (tag a person, add a comment about priority).

An approach that would fit your use case without being complex would be stolen from word processors: "new board" means "new blank board", but there is also "new from template", where the template could have tags, lists etc. predefined to suit your need.

[chris-NR]

The "clone" workaround almost works until you move a card between boards. If the card has a label e.g. "To review" on the original board it is not exactly the same label as that used on the clone. This means a user can add another label with the same name which results in a double label. I have not seen any other 'bad' effects so far...

[chris-NR]

A few thoughts on this....

A common scanario is:

1. Constant flow of 'cards' - ideas, support tickets, issues, risks etc
2. All cards of the same type have a minimum set of common labels e.g "High", "Medium", "Low"
3. A board is typically used to manage one type of card (e.g. issues)
4. The current design and cloning works very well e.g issue boards for particular groups (team, product etc) until you want to move cards between boards

Possible solution:

I agree that global tags would be both undesirable and expensive to implement. Assuming a label has board scope e.g. "BoardA->High" then a simpler solution might be something along these lines:

When a card moves from BoardA to BoardB if there is already a matching label on BoardB then replace the BoardA label with the corresponding BoardB label

[osm-frasch]

==> As an suggestion to the Deck-App-Dev's. To create 'Collaborative tags' from the 'Administration' 'Basic Settings' section so that all registered Users can use this tags in the Deck-App too. This would be a great enhancement for the Deck-App. So Process-Management is more straight forwards.

IMHO: In most cases, the media specialists in companies also have to map the processes in Nextclud project management. This way, they can create the necessary tags for certain procedures without having to explain to every employee where and how to create tags in the deck app. In addition, the tags would then really be the same for everyone in terms of colour and semantics.

[juliushaertl]

We should not introduce another global tag setting and instead follow the idea in #201 about reusing the nextcloud system tags for such a use case.