Currently, nested tags (hierarchies) in the Answer Library need to be created manually, exported, mapped, and then re-uploaded—an inefficient and error-prone process. If a new nested tag is added directly during an Answer Library import, only the parent tag is created, and the hierarchy is lost.
To streamline this, we propose either:
- Adding an import feature that supports nested tag creation directly from the Answer Library import process, or
- Implementing validation during import to identify and create nested tag structures appropriately.
This enhancement would significantly improve efficiency and accuracy for users managing large or complex tagging systems.
