Title: tree structure for templates
-
What is your original issue/pain point you want to solve?
Our ticket templates are increasing. The drop down list gets chaotic. -
Which are one or two concrete situations where this problem hurts the most?
ähm. yeah. creating tickets through templates (don’t know how to describe the “problem” better) -
Why is it not solvable with the Zammad standard?
Zammad simply has no tree structure for ticket templates. There is just a big list of templates i could use. -
What is your expectation/what do you want to achieve?
It would help a lot, if you have some “main” topics and dive deeper. the templates list gets clearer
I love the tree structure feature in groups and it would be very helpful if we have something similar for templates.
Your Zammad environment:
- Average concurrent agent count: 8
- Average tickets a day: 20
- What roles/people are involved: profesional service it technician, sales people and customers
we have some different customer templates with different topics. It would be great to sum up these templates per customer. Also we use Zammad for support tickets with our manufacturers. One big “manufacturer” tree where every single manufacturer is contained, would be great.
kind regards
Basti