The discussion revolves around enhancing tag group functionality in a ticket system. tknospdr seeks to enforce a sequential tagging workflow—Company, Priority, and Status—by making the ‘ticket’ tag the parent of the ‘Company’ group, and extending this logic so that each subsequent tag group is unlocked only after a tag from the previous group is selected. Currently, this requires manual intervention by support staff, and tknospdr proposes a plugin or theme solution to automate and ‘idiot-proof’ the process. pfaffman suggests using group flair or hiding tags via a theme component, but tknospdr clarifies that existing tag group restrictions are insufficient and requests a feature allowing tag groups to be conditionally exposed based on the presence of any tag from another group.
In my quest to make the perfect (for my use) ticket system, I want to force new tickets to be tagged in a certain order. I have 3 tag groups called Company, Priority, & Status. I want them to always be assigned in that order so I have a tag called ‘ticket’ and that’s the parent of Company.
It would be great if I could then have a parent like relationship so that I can’t assign Priority until Company has been assigned the same as ticket-Company works.
I know currently it’s an educational opportunity for our support staff, but anything I can do to idiot proof the workflow is a win.
Is there already something out there like this? Or is this just currently not possible?
They will mostly e-mail in to create their tickets, it’s how our current ticket system works.
Then when we’re notified of the new post, one of the support staff will edit it to add the ‘ticket’ tag, which then unlocks the other 3 groups of tags.
My ideal situation is that adding ‘ticket’ unlocks the ‘company’ group, adding a tag from that group then unlocks the priority group, which then finally unlocks the status group.
Tags already allow you to only allow a tag group to be used in certain categories, and you can also only allow a group to be used if the parent tag has been added.
I’m just suggesting that the parent function be extended to multiple parents by way of a tag group.
Only expose ‘this tag group’ if ‘any one of these tags (defined by a group)’ is already present.