Forms vs. Templates

Hello,

We are looking at a way to make manual ticket creation a bit more streamlined. We're trying to decide whether it's better to use the template feature or the forms feature. Currently, we have about 200 ticket types that we use. Some of them have forms on our Service Catalog and I'm currently leaning toward making forms for all of the different ticket types with information such as the responsible team, due date, affected group, etc. set to a default value in the form. This way, when a user contacts us directly, we can simply select the form and only have to fill out a brief title and description. This would also be beneficial as when we look to build out the Service Catalog further, we already have existing forms for our different ticket types.

Is this more or less correct? Is there any benefit to using ticket templates instead? I'm struggling to think of one.

Any more information is much appreciated, thank you!

Tags ticket forms tickets templates servicecatalog
Asked by Riley Fay on Tue 3/5/24 12:32 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Tue 3/5/24 1:53 PM

Hello Riley,

If you're truly looking at building things in a way that will be long-lasting into the future, I would recommend building these as Forms rather than Templates, just because I've heard various things about Ticket Templates eventually (no concrete time frame here, FYI) being phased out as a "feature".

If your work is truly unique enough that every ticket type represents an entirely different thing, then building a unique form for them to all be used on would make sense to me.

Sincerely,
Mark Sayers
Sr Support Consultant, CS

No feedback