My idea is:
Tags are a wonderful feature of Mautic however once created they cannot be renamed without modifying the database with SQL which I’m not opposed too doing its just time consuming.
However if you look at the database schema it appears that the tag id is not used throughout. Instead the tag name is used and this is why the tag name cannot be easily renamed via the UI. The name has to be changed in multiple tables etc
May I ask the the developers why this strategy was choosen. Normal database best practice recommends to use a foreign key rather than the name itself for precisely this reason ?
I would kindly ask the developers to consider changing the operation of tags and use foreign keys with a singe definition of the tag name so it would be easily changed by the UI.
I have also seen a plugin discussed at a Mautic conference to extend the functions of Companies which I tried but did not work for me. It appeared to have a separate company tag system. I would suggest that a redesigned tag database schema could be used for both a contact and a company - why have different tags schemas - when you can have one if properly designed. ?
As I continue my jorney with Mautic I’m constantly changing tag names to make them unerstandable and im sure many other users are frustrated by the fact that the tag name cannot be editied by the UI.
I know the developers are busy preparing Mautic 7 using Symfony 7 but I would say fixing limitation such as this one is more important to end users than changing the version of symphony as it hasn’t been a priority in the fast.
Thanks.